I wish to migrate a website to windows 2008 platform, is there any obvious pitfalls i should be aware of?
code base is c# 3.5,asp.net with ms ajax.
A:
Don't let the wacked user interface put you off (but it will drive you dilly)
Al
2008-09-19 15:38:36
I love the new UI, its great, lots of stuff there where you'd have to fire up Metaedit or start tweaking the Metabase.xml directly in IIS6.
AnthonyWJones
2008-09-21 20:50:12
It's just not great for the simple tasks that You want to do easily and quickly. For example, if you want to change the default directory of an existing site you have to walk the entire directory tree - it doesn't 'remember' the existing directory.
Al
2008-10-03 12:33:03
+1
A:
I googled a bit and found this link:
http://weblogs.asp.net/steveschofield/archive/2008/09/04/iis6-to-iis7-migration-tips-tricks.aspx
Biggest Issue i find is that 3rd party components needs to have 64bit version ready to get most of benefits.
Claus Thomsen
2008-09-19 16:24:28
+1
A:
I haven't had any experience with a migrated application not working properly. I've only done a few, but we've tested a number here at work, and they all run great under IIS7.
The only gotcha is that the .NET "Managed Pipeline Mode" is set to "Integrated" by default, which caused problems in some of our applications. Either setting it to "Classic" on your app pool, or switching your application to use the "Classic .NET" app pool should resolve the problem. For some more information about the new pipeine, read about it here.
Oh - and +1 on the wacked-out interface. I want my old IIS6 interface back!
rwmnau
2009-01-13 22:27:06