.NET Framework 4 RTM on Windows server 2008 R2

.net-4.0netwindows-server-2008

I've just installed .NET 4 on Windows SErver 2008 R2 x64 and I am getting 500 Internal Server Error with an ASP.NET MVC application which was previously running fine on 3.5. The application was upgraded from targeting 3.5 to target 4 and I personally built it today on my development machine (changed in VS – Properties to .NET Framework 4).

On the server I installed .NET Framework 4 Client profile and Full both automatically through the Web Platform Installer. ASP.NET MVC 2 was also installed through Platform Installer. I created a new .NET 4 application pool in IIS and placed the web app in it.

Also I have custom errors turned Off in web.config but even so no detailed error is displayed – just the plain IIS 7.5 500 Internal Server Error.

Any suggestions?

Best Answer

Well, that's a very strange and interesting issue.. But I'm eager to help as much as I can. I've currently got a VPS with Server 2008 R2, and I've installed .NET 4 RTM, and MVC 2 on it. Don't think I've run into configuration issues, but I have had to help set up some other people with it..

Initially, could you check.. in your IIS manager, Isapi and Cgi restrictions, do you have .NET 4 in there? Which versions? are they enabled?

If you go to your app pools in IIS, are your app pools ser to .NET 4, the NEW version? Double check this, your app pools might be set to a different build of the .NET 4 framework, that has since been removed / disabled. You can try create a NEW website with a new clean app pool just to test if it works.

If nothing works yet, you can try to re-register .NET in IIS with aspnet_regiis -i

If none of these work, I'll try to come back with some more options/ideas

Related Solutions

.net – Difference between decimal, float and double in .NET

float and double are floating binary point types. In other words, they represent a number like this:

10001.10010110011

The binary number and the location of the binary point are both encoded within the value.

decimal is a floating decimal point type. In other words, they represent a number like this:

12345.65789

Again, the number and the location of the decimal point are both encoded within the value – that's what makes decimal still a floating point type instead of a fixed point type.

The important thing to note is that humans are used to representing non-integers in a decimal form, and expect exact results in decimal representations; not all decimal numbers are exactly representable in binary floating point – 0.1, for example – so if you use a binary floating point value you'll actually get an approximation to 0.1. You'll still get approximations when using a floating decimal point as well – the result of dividing 1 by 3 can't be exactly represented, for example.

As for what to use when:

For values which are "naturally exact decimals" it's good to use decimal. This is usually suitable for any concepts invented by humans: financial values are the most obvious example, but there are others too. Consider the score given to divers or ice skaters, for example.
For values which are more artefacts of nature which can't really be measured exactly anyway, float/double are more appropriate. For example, scientific data would usually be represented in this form. Here, the original values won't be "decimally accurate" to start with, so it's not important for the expected results to maintain the "decimal accuracy". Floating binary point types are much faster to work with than decimals.

R – .NET Framework version issue

To answer the comment that George2 has left to each of the other answers in one place:

Yes. The Common Language Runtime is what needs to be 2.0 (and cannot, currently, be higher, since that's the latest at this time).

Yes. You can think of the .NET Framework as the SDK if that makes it easier. It's not quite accurate, but....

Yes. You will be deploying your Framework 3.5 functionality on the CLR 2.0. Confusing, but that's Microsoft for you. They do (some) great work, but seem to delight in confusing users with arbitrary versioning.

Best Answer

Related Solutions

.net – Difference between decimal, float and double in .NET

R – .NET Framework version issue

Related Topic