I am not sure if this is the correct thread to be posting this, but here we go.   I work at an office with several people who develop DNN modules/sites using our terminal server.  We are constantly working with different versions of DNN using the same VS2005 installation.

We really like using the Starter Package with DNN and Visual Studio 2005 because it makes initial site/module creation very simple.  The problem is, when we start a new site we like to use the latest stable DNN version.  If we install the new starter package on our terminal server, the template description in VS2005 does NOT include the version number and instead replaces the existing template.  It prompts to rename the zipfiles to Skin(3).zip etc, but there is nothing on the GUI side of VS2005 to signify a version change.  This ends up with people putting 4.8 modules into 4.35 sites.  Ultimately I am forced to go in and manually edit the entries in each of the zip files and the .vscontent file to reflect what version I'm installing.

I have been working with DNN for over a year and I am very surprised to find this has not been implemented yet.  It is very annoying to have to go in and edit those file (not to mention I'm not sure I'm doing it correctly anyway, although it seems to work).    Is there something I am missing here that would allow for multiple templates, with different versions, to be installed on an instance of VS2005?  Or am I stuck going in and editing these files with EVERY release?

I love DNN and it's a great framework.  I just wish there was an easier way to maintain templates of different versions in VS.

Thanks everyone!