Visual Studio: What approach do you use to 'template' plumbing for similiar projects?

Posted by Sosh on Stack Overflow See other posts from Stack Overflow or by Sosh
Published on 2010-03-31T09:45:04Z Indexed on 2010/03/31 12:03 UTC
Read the original article Hit count: 266

When building ASP.NET projects there is a certain amount of boilerplate, or plumbing that needs to be done, which is often identical across projects. This is especially the case with MVC and ALT.NET approaches. [I'm thinking of things such as: IoC, ORM, Solution structure (projects), Session Management, User Management, I18n etc.]

I would like to know what approach you find best for 'reusing' this plumbing accross projects?

  • Have a 'master solution' which you duplicate and rename somehow? (I'm using a this to a degree at the moment, but it's fairly messy. Would be interested how people do this 'better')
  • Mainly rely on Shared Library projects? (I find this appropriate for some things, but too restrictive for things that have to be customised)
  • Code generation tools, such as T4? (Similar to the approach used by SharpArchitecture - have not tried this myself)
  • Something else?

Thanks for sharing your experiences!

© Stack Overflow or respective owner

Related posts about asp.net-mvc

Related posts about visual-studio