So I've recently spoken to some old colleagues about how they use SVN to release their site code and realized that there is still not a lot of common use of a release process. They suffer due to their time constraints since they've had little time to review and it can be daunting to take on the task of redefining a new aproach to this technology if you're really crunched for time. On the other hand, it can also be very nerve wracking when you're pushing code by updating a folder because if there's an issue a code roll-back is manual. I've been shown a solution to this challenge myself so I thought it would be good to put up an article giving an easy straight forward way for you to upgrade your approach without too much difficulty. If you can't retrofit your project in the way I'll show, you should be able to at least find another way once you understand the principles behind it.
When it comes to working with .NET on the web you have a lot of flexibility on how you approach a project. One particular aspect which seems to be a constant point of contention is the differences between Visual Studio's Website (WS) and Visual Studio's Web Application project (WAP). I had to work with both and over a long time and lot of arguments I learned quite a bit about the differences. Almost anyone who has written an article about this will tell you that you can accomplish pretty much any task with either approach and that choosing one over the other really comes down to your preference and situation. I started working on the WS model and have found that it is suitable for some tasks but the longer I develop the more I find myself using the WAP model because the environment and tools it offers tends to help me accomplish my goals faster and with more precision. It should also be noted that both project types are still reliant on IIS and the model type you choose really only changes the way you work with the project, not how IIS views the files. It's more a difference in the paradigm the two offer.