Upgrading to .NET Framework 4.0

Ah! The joy of upgrading to bleeding-edge technology... Makes you bleed!

So, we've recently upgraded from WindowsXP, VS.NET 2008, SQL Server 2005 and on to the glorious OS of Windows 7, VS.NET 2010 and SQL Server 2008. I have to say I really enjoy the new features of all the new upgrades.

There's always that "However, ...", so here it goes....

However, we're still running Windows Server 2003 and SQL Server 2005 - so, that presents some challenges.

First things first - download and install NetFx 4.0 or search Google for NetFx 4.0. Once you

finish installing it you'll need to run AspNet_RegIIS -i to register the .Net Framework 4.0 with ASP.NET. You'll need to enable v4.0 for ASP.NET by opening IIS Manager. The way I like to get to the IIS Manager Console is by using my keyboard short-cuts. Press the Windows Key+R, type InetMgr and press Enter.

Expand your server node, select Web Service Extensions, select ASP.NET v4.0.30319 and press Allow.

Now, you'll need to go over to your Web Site or Virtual Folder, right-click and select properties. Click on the ASP.NET Tab and select 4.0.30319 on the drop-down for ASP.NET version.

Now you're ready to run your website!

A few things to watch out for... Or rather a few problems we ran into.

1. Crystal Reports - The beta version is only in 32-bit version which won't run on a 64-bit server. You'll need to install the 64-bit RTM Version of Crystal Reports. There is no 32-bit version for the beta. Hey, don't curse me - I'm just the messenger.

2. IIS6 in 32-Bit mode - We tried this and it cause more head-aches than it was worth. If in fact you really need to run in 32-bit mode be aware that the WHOLE SERVER will run in 32-bit mode. We couldn't find a way to run both 64-bit and 32-bit side-by-side on the same server. Another problem we found was that we lost the ASP.NET Tab from the Web Site Properties. Even after disabling 32-bit mode we couldn't get it back. If you run into this problem you can serach Google for "asptabtest" or "aspmantst" - it's a few files that will run some automated test to recover the ASP.NET Tab (we used it with plenty of success). Keep in mind that this will only recover the tab when 64-bit mode is enable and 32-bit mode disabled.

3. IIS7 in 32-mode - This is not the case on Windows 7 and Windows Server 2008. At least for Windows 7 you can setup an Application Pool to allow 32-bit Applications. I haven't had the luxury of setting it up on Windows Server 2008.

I hope this helps save several hours of Google'ing - for everything was so spread out throughout the internet.