Hi
I’ve come to the conclusion that a C# MVC 5 project (using Entity framework, code first and migrations) I’m working on has grown too big to fit the “out of the template” structure.
I’m trying to build a site where the public part at the site is placed in the “root” or where a site build on the VS MVC 5 template would reside. In this root authentication logic will be handled. The plan is to build a series of modules placed in areas, that each offers a specific set of functionality e.g. a project management tool, an accounting tool, blog tool – all fairly basic or simple tools that I over time develop out of interest for public use, but all hosted with my site as root. The main rule for the areas is that they don’t share anything with each other except authentication and authorization.
I’m therefore looking into implementing the following things:
- Repositories and “Unit Of Work”
- A mapping tool (preferably ExpressMapper) for mapping between models and viewmodels.
- Dependency injection using an IOC container (preferably Unity)
Can anyone point me in the direction of good videos, articles or blogposts on the individual subjects above or even better if more than one of the subjects are covered at once. References to code samples would be really nice, but I fear that’s too much to ask for?
Thanks in advance for your input.
What I have tried:
I’ve scoured the internet for good videos, blogposts and articles that describe this in a way a novice to these this can understand and hence implement in my project. Unfortunately I haven’t found any really good info that I’ve been able to piece together to a working “base” that incorporates all of the above, upon which to build my code.
Submit an article or tip