Reducing development time on ASP.Net MVC

Question

I am starting new medium size ASP.Net MVC project. There will be 50-60 tables. IE: employee tables(assigning training etc/) , basic warehouse management,. There wont be complicated workflows also.

I am looking for the ways to reduce my development time.

Scaffolding is a good starting point but hard to manage.

I could not decide about using AngularJS SPA or not, Using angular JS reduce the development time ? Or what is the advangates of using angular ?

What is your recommandations about reducing the development time on ASP.Net MVC projects, which ways are you using to building medium size applications.

Answer 1

I don't know your experience with MVC, but generally speaking, I'd suggest to use a UI Framework (like Telerik, DevExpress or Aspnetawesome) because they offer plenty of example on how to organize your project. It definitly saves you time. Then which one you choose depends on your preference and budget. All 3 are good.

As for managing your data, just create a Domain project which will only contain your data access (probably repositories). For that project, it is no different from a normal C# project. You'll probably want to use Entity Framework, nHibernate or a similar ORM.

So to recap, divide your solution in at least 2 projects, one for the data and one for the UI, then use a UI framework for the MVC project and an ORM for the data access.

As for AngularJS, I would not focus on such tool unless you are really comfortable with MVC.

Pros:

• On the long term, you may save some time
• It is free
• It is well supported and seems to be there to last

Cons:

• If you are part (now or eventually) of a team, not all members will know that tool
• If you are comfortable with MVC, this will not save you significant time in my opinion. You don't become an MVC superstar because of it
• If you are not that comfortable with MVC, incorporating such tool is a bad idea. It is better to know a few tools but to use them properly than to poorly use many of them.