1. Running 32-bit and 64-bit ASP.NET versions at the same time on different worker processes
2. WebSite Not starting (Error : iis website error : value does not fall in expected range)
Solution: A. Also, in the configuration editor, delete all keys
If still fails
B. Delete all the VDs under it and create new ones after starting site
3. is there 32 and 64 bit iis 7
Solution : NO, u can only do step 1 & 2 above to accomplish this.
4. when i began, i got this error :
“Register ASP.NET 4.0 on the Web server”
5. microsoft.net Framework vs Framework64
6. ASP.NET Web App Build Target
The issue here is that i am changing the machine.config file and didn’t know which to change….Now i have a asp.net website and in its visual studio build setting of Platform Target, i’ve set it to Any CPU
Any CPU is always an option, as you point out. That will allow the application to run as a 32-bit application (x86) on a 32-bit machine, and as a 64-bit application (x64) on a 64-bit machine.
An AnyCPU assembly will JIT to 64 bit code when loaded into 64 bit process and 32 bit when loaded into a 32 bit process.
By limiting the CPU you would be saying there is something being used by the assembly (something likely unmanaged) that requires 32 bits or 64 bits.
CATCH : I think most of the important stuff has been said, but I just thought I’d add one thing: if you compile as “Any CPU” and run on an x64 platform, then you won’t be able to load 32-bit dlls, because your app wasn’t started in WOW64, but those dlls need to run there. If you compile as x86, then the x64 system will run you app in WOW64, and you’ll be able to load 32-bit dlls. So I think you should choose “Any CPU” if your dependencies can run in either environment, but choose x86 if you have 32-bit dependencies. This article from Microsoft explains this a bit:
8. Finally resolved another confusion : IIS Manager vs iis express