Issues that occur after the program is upgraded to 4.0:
IIS application pool configured to 4.0 Classic error: HTTP error 500.19-internal Server Error Error resolution
Configured to 2.0 Classic when reported error: Failed to load file or assembly "System.Xml.Linq" or one of its dependencies. The runtime that generated this assembly is newer than the currently loaded run and cannot load this assembly.
For example, IIS typically returns the error message to the client.
SYSTEM.XML.LINQ (other assemblies are the same) configured to 2.0 when the error is due to the program upgrade, referring to 4.0 System.Xml.Linq.dll, you can directly remove 4.0 of the DLL directly re-reference 2.0
But System.Xml.Linq.dll is in. NET framework3.5. 3.5 is a series of extensions of 2.0, essentially running is the 2.0 version you just choose 2.0, and on the machine to confirm that there is 3.5 of the framework, you can run 3.5 of the site
NET framework3.5 Some questions refer to: http://blog.csdn.net/zanychou/article/details/7195646
Workaround: Simply delete the 3.5 reference in Web. config According to the returned error message. Such as:
In fact, 3.5 in the Web. config can be completely deleted, leaving only their own configuration on it.
For example: the initial 4.0 Web. config
The following is the registration of the framework:
32-bit Windows:
---------------------------------------------------------------------------
1. Running->cmd
2. CD C:\Windows\Microsoft.NET\Framework\v4.0.30319
3. Aspnet_regiis.exe-i
64-bit Windows:
---------------------------------------------------------------------------
1. Running->cmd
2. CD C:\Windows\Microsoft.NET\Framework64\v4.0.30319
3. Aspnet_regiis.exe-i
HTTP Error 500.19-internal Server Error resolution method