Resolving Circular References (C#)

Answer 1

The question comes down to what you separate by namespace and what you separate by DLL. If you have a good reason to keep EVERYTHING modular, you have to work really hard. But if each of these dlls only have a class or two in them, perhaps you could merge them together?

Answer 2

Take a few minutes and sort out the procedures ... create an identifier for each project (FM, FS, FD, FU). List each publicly accessible procedure on a page and then add an identifier for a project, if that project uses the procedure ...

Then you can see which procedure needs to be in (or accessible to) which project.

Hope that helps!

Answer 3

Use interfaces for all non-trivial classes. Place interfaces in a different assembly from implementation.

Answer 4

1. You can put your localized email strings in Flip.Services. The downside is that you have two places to maintain localized resources. You can also have a separate dll for all your resources to minimize the place to edit resources.
2. You have to move the fluent interface to an other dll or make CustomerSearchFilter part of the domain.
3. You will need to add more projects or rearrange your structure and use namespaces to create the separation.

Answer 5

It sounds like your building on concrete implementations instead of interfaces/contracts. As Ima suggests define interfaces that describe what a certain class should be able to do. Use this interface when you declare properties, parameters and the like. Keep the interfaces separate from the implementaion and both the implementation and the projects that uses the interface can reference the interface project.

You then get the nice option of using dependency injection making your code easier to test as an a side

Answer 6

In the "tiers" of a domain, repositories and services live at the same logical level, above the domain in an infrastructure role. I would suggest moving your repository implementations (queries, etc.) outside of the domain itself. That solves #2 at least.