Search code examples
asp.netproject-structure

Should the UI reference the Repository?

I have four assemblies; UserInterface, BusinessLogic, DataAccess, Common.

The User Interface references the Repository that is in the DataAccess, is that bad practice? Should I create pass through methods in the BusinessLogic so that the UserInterface is not coupled to the DA assembly?

Even in cases where the BusinessLogic method does nothing but call the relevant Repository method?

Or am I being pendantic?

Solution

  • rather than think of the UI talking to the repository, think of implementations depending on abstractions. in this instance the UI depends on IRepository. How IRepository is implemented doesn't matter.

    and putting this all into separate assemblies is overkill. just use namespaces to segregate your code. it will be much easier to maintain.