We help IT Professionals succeed at work.

Best Practice website versioning (ASP NET)

kenpowata used Ask the Experts™

I would like to know what would be the best practice to create a website with versions.
To make it clearer, i think of putting the website versions inside subfolders "v0, v1, etc..", and the "content" in a separeted folder, like "data".
The user should be redirected directly to the current version if the url dont specify the version.[Would be best to use url routing or url rewrite?]

Im using ASP NET and im new to it. So i dont even know if its better to use web site, web application or MVC.

what is recomended to make a website with easy versioning.
[Another thing that bugs me, is that web site deployment deletes the target folder content, so i now im working(learning) with web application.

Any advice is welcome, even if its not directly related to my question.
[Sorry for my english, its not my native language]
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
what would be the reason of keeping the older versions?  separate user exeriences?  if it's just for reverting purposes I would suggest just to make incremental backups prior to updating the site


Yeah, what you said is true, i cant point out a good reason to keep online diferent versions of a website.

I am learning and doing a lot of test cases, so keeping diferent versions of the website online helps me to compare the behavior of the webpages in the host. [thats the reason]

My dificult is more about redirecting the user to the correct page [url rewrite or url routing] and about deployment advices.
Aaron TomoskyDirector of Solutions Consulting

Once you get into versioning, it's time for subversion, or git. Plenty of free or cheap svn hosts, collabnet / ubersvn is free and easy to install yourself.


The answer helped me with my doubt, but didnt resolve my problem with good practices for redirecting the client request or about deployment advice