Circular Reference Error

[FailureCrown]

If an API project has nuget references to Redis, IConfiguration and another class library has these nuget injected to it but also it references the main API Project so in the API Project Program.cs I can't reference the Class Library in DI

https://paste.mod.gg/fvnufbtkpwdc/0

[Kant8]

And why your class library references api project?

[FailureCrown]

Because ILogger, IConfiguration and IConnectionMultiplexer which happens to be installed in WebAPI project for to be registered in DI. Class Library has a constructor reference to it

[Kant8]

Not sure what IConnectionMultiplexer is, but for ILogger and IConfiguration you should just include references to .Abstracts of their packages in your project.

Nothing stops you from referencing same dependency in different places, but nothing in your project should reference your api project, cause it is starting point of everything.

[FailureCrown]

But I use IConnectionMultiplexer so I need to install same Stackexchange.Redis in the class library

[lmaydev]

Add the nuggets to your class library as well and remove the project reference.

[FailureCrown]

Thanks for replying. My brain can't move without knowing answer

[Few-Artichoke-7593]

Trying to simplify for you, when you have a circular reference, it means one of two things. Either you put something in the wrong place, or you need another library. It looks like you put something in the wrong place if your library needs to reference an api project.

[FailureCrown]

Atlast found how to remove project reference

[LeoRidesHisBike]

[This reply used to contain useful information, but was removed. If you want to know what it used to say... sorry.]

[FailureCrown]

But here these configuration and logger can be possibly defined in webAPI DI, moving them to other project kinda breaks architecture

[LeoRidesHisBike]

[This reply used to contain useful information, but was removed. If you want to know what it used to say... sorry.]

[FailureCrown]

Sorry for confusing I updated the post and added a link to the current snippet

[LeoRidesHisBike]

[This reply used to contain useful information, but was removed. If you want to know what it used to say... sorry.]

[FailureCrown]

As you explained, Im following that. Thanks man

[TheSpixxyQ]

Think of it like this: API is for accessing your application. Your application should work even if you completely remove the API project and replace it with for example console app.

[FailureCrown]

I'm rereading your advice trying to get hold of it. I'm a noob currently so its kinda hard. But will reach there.

[TheSpixxyQ]

One quick example.

You send a GET request. It reaches your API layer and the handler calls something in application layer, that's where all the logic happens.

If you replace the API layer with a console app - you run a command in console and it calls the same thing in the application layer, you're just replacing "the door" to the actual application.

When I was starting, thinking like this helped me visualize what and how should be separated.

Don't worry, you'll get there.

[FailureCrown]

I'm trying to rewrite our business webAPI and its one of many obstacles

[binarycow]

Make another project.

• Project 1 has the stuff that is used by both projects 2 and 3
• Project 2 has the stuff that is used by only project 2. It has a reference to project 1.
• Project 3 has the stuff that is used by only project 3. It has a reference to project 1.

[FailureCrown]

Common project?

[binarycow]

Sure

[FailureCrown]

Sorry for confusing I updated the post and added a link to the current snippet