Last post Nov 19, 2012 12:12 PM by ojm37
Nov 14, 2012 10:15 AM|ojm37|LINK
Does Microsoft have a "Best Practice" for deploying a Web Site project (NOT a Web Application project - various reasons we won't go into here) to IIS 7 on a Windows Server 2008 host? We are using VisualStudio 2012 and Team Foundation Server 2010 (upgrading
to TFS 2012 in the near future) for our new development. Old code still uses Classic asp.
We've been using Visual Source Safe to "get" all our changes to the server (after thorough testing on both development and staging servers). This has worked well for many years. However, with the demise of SourceSafe and our adoption of Team Foundation Server,
we're running into problems with this method.
It would be nice if we could deploy simple changes (like to just one or two files) without taking the web server (and our site) down for the duration of the deployment. (Visual Source Safe method made this easy).
So, how do other people do this (deploy chages to their website)? Do you do it without site downtime? Does Microsoft have an "approved" method?
Nov 19, 2012 12:06 PM|cts-mgraham|LINK
For web applications, we have Web Deploy 3.0. You can read about it and download it here:
If you are looking for something more like VSS, you might want to post this to the Team Foundation Server
forum - they might have something better.
Note - if this is just classic ASP code, any way you can copy the files to the server would work. Be aware that a change to the global.asa or anything in the bin directory would be detected and the appDomain would be unloaded (users will lose session variables,
and depending on the application you can expect other issues consistent with an IISRESET).
Nov 19, 2012 12:12 PM|ojm37|LINK
OK, Thanks. I'll ask over on the TFS site.
I'd like to have a web application, but that's just not going to happen ... We're stuck with a web site project...