You can't run ASP 1.1 applications under an ASP 2.0 root
Originally posted this over on my personal blog, but it seems relevant to what people might run into when doing ASP.NET migrations, especially in more complex scenerios.
Well, apparently you can't run a 1.1 ASP.NET application under a ASP.NET 2.0 root. IIS Manager allows you to set the target framework at the application level, but the 1.1 application will still bubble up through the 2.0 web.config and fail to validate. What I haven't determined is whether it works as long as your 2.0 web.config doesn't have any 2.0 specific entries. This seems unlikely since for a lot of the new features you need new config entries and I think some of the structure changed as well, so my gut is it just won't work. So until I can get Community Server running under ASP.NET 2.0, I can't use my standard blog set up. The guys at WebHost4Life recommend setting it up as a subdomain and setting the version on the subdomain. This works because IIS treats the folder as a root node and so it sticks with ASP.NET 1.1 and works fine. The only problem is in the meantime I lose all my inbound links, feed subscriptions, etc which sucks. So much for the little bit of Google juice I had. I'll probably be able to go back to the old links at some point, but for now you'll have to hit my personal blog using:
http://blog.swartzentruber.net/CurtBlog
Please update your RSS aggregators and links accordingly. Here is the new direct URL to the RSS feed
CurtBlog RSS
Oh and I can't do a redirect with an Http 301 Response because if I could get that working, I wouldn't have this issue in the first place. People are going to have similar issues with nGallery, which I also use, as well as apps like DotNetNuke.