I’m sure you already know about this fix for ASP.NET which fixes an issue of “not a valid path” exception, and this fix for ASP.NET 1.1 for the same reason. If you receive this error now on your application, you might not need to apply the hotfix because your ASP.NET version might be higher than the one available with this hotfix, so verify the DLL versions before even requesting the hotfix from Microsoft. So, after installing the hotfix, you should do the below registry changes (not sure if the hotfix does this automatically – I haven’t tested this): DWORD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\VerificationCompatibility = 1 as mentioned in the KB article 932552 . But, you might see that this doesn’t work if you run the application pool under 32-bit mode on a x64 Windows Server 2003 or 2008. That’s just because, the ASP.NET reads this key from a different location as below: DWORD HKEY_LOCAL_MACHINE...
The Microsoft.com Operations Team is pleased to announce the launch of our new Microsoft.com Engineering Operations TechCenter . This site ids designed with the ITPro/Systems Engineer in mind. We get to work on some cutting edge technologies and our goal Read More......( read more ) Read More...
When running on x64 hardware, you have two options. First, to run in native 64-bit mode. This means all the applications running need to be 64-bit. The second is to run worker processes in 32-bit mode, which means all applications need to be 32-bit. This gives you good compatibility and performance is really good too. Here's how to install the 32-bit or 64-bit versions of ASP.NET, as well as the option you need to run for IIS to get them working. http://support.microsoft.com/kb/894435...( read more ) Read More...