Krokonoster
May 29th, 2010, 11:44 AM
I did mention this before, but figured start a new thread so the responses are in one place.
I started with this “template” project using Asp.Net MVC 2, .Net 4.0, C# and VS 2010 (with Resharper doing the baby –sitting).
You can download it here (http://www.krokonoster.com/)
The idea was to create a solution that I can use as starting point for pretty much any application (or at least parts of it) and I got to the point where I better get things organized before going on (not to mention tested!)
Was hoping to share this and perhaps we can learn from each other? So bring on the critic (constructive). :rolleyes:
Please bear with me, as even though I’ve been using Asp.Net MVC for a while, I must split my time between PHP and Java (not to mention front end development), so got some gaps in my knowledge.
The main thing I know just have to be wrong is the project structure.
Also I’m not too confident about my way of using View Models, and manually converting that to domain models. (AutoMapper I tried in another project and it soon turned into a nightmare)
IoC (Castle) are in place and working, along with BootStrap tasks for registering things. (Routes, Areas, Model Binders, etc)
A Custom Membership provider are in there and being used (I like the fact I only use 3 tables and can customize things depending on a specific application requirement)
Implemented AntiXssEncoder
Implemented Login, Register, View Membership details just to see all that works fine
I think the main thing I want to get sorted out at this stage is the project structure. Any advice on how to change the solution to have it be loosely coupled and scalable will be welcome.
I know I should work on commenting my code and get Code Coverage via Tests up (naughty naughty)
Let me know what you think.
I started with this “template” project using Asp.Net MVC 2, .Net 4.0, C# and VS 2010 (with Resharper doing the baby –sitting).
You can download it here (http://www.krokonoster.com/)
The idea was to create a solution that I can use as starting point for pretty much any application (or at least parts of it) and I got to the point where I better get things organized before going on (not to mention tested!)
Was hoping to share this and perhaps we can learn from each other? So bring on the critic (constructive). :rolleyes:
Please bear with me, as even though I’ve been using Asp.Net MVC for a while, I must split my time between PHP and Java (not to mention front end development), so got some gaps in my knowledge.
The main thing I know just have to be wrong is the project structure.
Also I’m not too confident about my way of using View Models, and manually converting that to domain models. (AutoMapper I tried in another project and it soon turned into a nightmare)
IoC (Castle) are in place and working, along with BootStrap tasks for registering things. (Routes, Areas, Model Binders, etc)
A Custom Membership provider are in there and being used (I like the fact I only use 3 tables and can customize things depending on a specific application requirement)
Implemented AntiXssEncoder
Implemented Login, Register, View Membership details just to see all that works fine
I think the main thing I want to get sorted out at this stage is the project structure. Any advice on how to change the solution to have it be loosely coupled and scalable will be welcome.
I know I should work on commenting my code and get Code Coverage via Tests up (naughty naughty)
Let me know what you think.