I am trying to come up with a way to deploy ASP.NET code with as little site disturbance as possible. One thought was to set up the site to be served from an NTFS junction
c:\www\example.com -> c:\www\example.com_r1234
Then, when new code is deployed, it gets copied to
c:\www\site.com_r1235 and the junction retargeted to
c:\www\example.com -> c:\www\example.com_r1235
So my question is what affect this might have on current requests in IIS? What other drawbacks might this have from the point of view of IIS's reaction to the change (if any)? Will this be as seamless for the end user of the site as I hope?
(I've considered changing the site's web root through the command line, but I really don't like the idea of reconfiguring IIS because of any unnecessary app domain or app pool churn that might happen, but I don't know a lot about what happens when the configured physical path of a site is changed while under load)
To be clear, my only concern here is the experience of my end users. My aim is to avoid disturbances for them, not convenience for me.