What is in the service layer?
A Service Layer defines an application’s boundary [Cockburn PloP] and its set of available operations from the perspective of interfacing client layers. It encapsulates the application’s business logic, controlling transactions and coor-dinating responses in the implementation of its operations.
Why do we use service layer?
The service layer is there to provide logic to operate on the data sent to and from the DAO and the client. Service layer provides code modularity,the business logic and rules are specified in the service layer which in turn calls DAO layer ,the DAO layer is then only responsible for interacting with DB.
Can you use di to resolve circular dependencies?
Yes. You can use DI to resolve circular dependencies. The first step to fixing any issue is finding it. Ninject complained about my circular dependency and threw a helpful exception at bootstrapping. Ninject found it for me and is forcing me to fix it.
How to resolve circular dependencies between.net assemblies?
I’ve seen several articles on various websites that propose resolving circular dependencies between .NET assemblies by using dependency injection. This may resolve the build errors but it’s not really resolving the circular dependency, is it? To me, there seems to still be a logical error in the architecture. Am I crazy or do others agree?
How to solve circular dependencies between two objects?
If you have circular dependencies between two objects, it means you need a third object, on which the two objects will depend on, so they won’t depend on each other. Here is an article that is the exact solution to your problem:
Is it possible to hide circular dependencies in.net?
Yes, you make it even harder to detect them by using an extra layer of abstraction. You absolutely do not solve the circular dependency but hide it by adding an extra layer of abstraction, using late bounding, or/and loosely coupling it.