I am taking an ASP.NET project from .NET 3.5 to .NET 4.
Everything works if I'm debugging in web.dev (i.e. Visual Studio [2010]), but as soon as I try and run under IIS 7 [.5] The debugger fails to attach. Under the IIS, the project is being run directly, so that it causes 403 S (not any subcode, hence not much help there) to throw back.
I present the site current (and working!) .net 3.5 site AppPool with the .NET 4 runtime. I have confirmed that all file permissions are Kosher (at least from .NET 3.5 perspective). I feel like I'm losing some configuration steps here ...
The error message is just "Unable to start debugging on the webserver" while trying to attach the debugger. Not the most useful error message in the world.
Attaching directly to the related w3wp process gives very little suggestion that the application has never been successfully completed.
The basic question is, how do I affect this change from .NET 3.5 to .NET 4 for the ongoing project under IIS?
This figure out.
.NET 4 was not established for IIS purposes. Do not ask me why this was so.
Running asp_net_regiis -i in Visual Studio under the .NET 4 Installed Directory (\ Windows \ Framework \ v4.0.xxxx) command prompt (in my case x64 ) Problem solved
Comments
Post a Comment