c# - Circular Dependency in an inherited code base -

i'm still learning how structure larger code bases (a year ago had dealt in solutions of 3/4 small projects whilst learning), , i've been trying organise inherited code base rid of circular dependency issue.

basically have mvc portal project backed sql database code first using entity framework. have repository project handles communication azure tables. data in these tables overlaps azure table not contain of information portal db.

the problem arises when create entities, solution demands created in portal database (so users can see information) , in these azure tables rest of solution uses other purposes.

so portal persists data both, meaning need use repository project within mvc project, need repository project able access mvc project peripheral information not persisted azure tables.

this bad design, structurally there way around doesn't require major refactoring or changes azure table structure include every little detail of portal db?

every "simple fix" come isn't fix @ , merely makes circle bigger haha. these 2 tables in design have confused me since inherited this.

edit more clarity

my repository references mvc project in order use applicationdbcontext communicate portal db. not separated project understand. mvc project references repository store information in azure tables. needs stay really.

tha problem guess repository much. i'm starting think should separate out despite being quite rework.

jk

correct me if wrong, understood, want exchange information between azure storage , sql storage. if case, should create baserepository inherited both sql , azure storage. "peripheral information" can found in properties baserepository, accessible children.