I have a problem where I can get an MVC2.0 application using .NET3.5 running in IIS, but when I upgrade it to .NET4.0, the browser just reports error 500 Internal Server Error.
The problem is easy to replicate as follows. Firstly, to show it works with .NET3.5:
Create a new MVC2.0 application in Visual Studio 2010, using the inbuilt starter template.
Run the application using the development server, and the Home & About pages display fine.
Publish the application to a directory.
Copy the directory to a subdirectory under inetpub/wwwroot on my Vista computer, running IIS7
Create a new application in IIS Manager & select the DefaultAppPool (integrated pipeline)
Browse the application and Home & About pages are displayed.
Then the problem I have is after upgrading to .NET4.0:
Change to .NET4.0 for the project in Visual Studio
Build & this runs fine with the development server.
Publish the application & set up IIS as before, except choosing the application pool ASP.NET v4.0 (integrated pipeline)
Browse the application, and I get the 500 Internal Server Error
I'm guessing there is some extra configuration required - can anyone help?
I've deliberately used the default MVC installation to eliminate any variables caused by my programming ..
Thanks in advance,
View Complete Post