Last post Jul 27, 2014 10:17 PM by BetsyASP
Jul 24, 2014 03:39 AM|pavanpuligandla|LINK
I've created a project structure using MVC 5(CastleWindsor for DI and logging) as front end, Services layer(web api's), Repostiry layer, Data Access, Model (with EF 6) based on the code project site post. Now i decided to go with NHibernate and AutoFac
for DI. Attached the screenshot of my project structure.
Can anyone please review it and let me know the correct architecture..
Image Path :
Edit : I want to use N-tier architecture to get implemented for this.
Awaiting your responses
Jul 27, 2014 10:17 PM|BetsyASP|LINK
If you are already familiar with ASP.NET
MVC, you have probably seen the
repository pattern in a few examples (such as
NerdDinner), maybe you even use it in your own app.
One of the most frequent way to hot-plug a Repository class into a controller is to use the Strategy
Pattern. But while an application evolves, you might want to centrally manage your wiring within a provider, that's what Dependency Injectors are for. However, lots of Dependency Injectors - or IoC containers at large -
such as Unity or Castle Windsor contain a plethora of features and often rely heavily on XML configuration, making them overkill for smaller projects.
Ninject makes it relatively effortless to set up a DI. It just reached version 2.0.
In this post we will see how to:
More information please refer to: