We like to put new versions of live ASP.NET websites in version-numbered folders.
Hitherto, that involved updating the IIS metabase so that the web site or web application "physical path" would point to the new location.
I thought it might be a little easier to use mklink to create a directory symbolic link or a directory junction with a name that I don't change (e.g. "curver" for "current version"), pointing to whatever is the current website version folder at the time.
It doesn't work.
For directory symbolic links, ASP.NET seems to totally fail to use them properly. Instead of getting the output of each ASPX page when visiting it in a web browser, I get the ASPX source!
For directory junctions, ASP.NET seems to use them just fine, but at the point you update where the directory junction points to, it's hit & miss whether ASP.NET will notice the change or not. If you're happy to trigger a restart of the website in IIS, then it works but if you're back to mucking around with IIS (i.e. to trigger the website restart), you might as well stick to updating the "physical path" setting of the website.
Conclusion? It was worth a try - would've been nice if it worked, but it doesn't.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment