#17728: Workaround asp.net bug loading incorrect version of System.

Some of our assemblies in "~/bin" reference "System, Version=2.0.0.0".
During the first time site compilation in the command line scenario,
asp.net will sometimes decide to load that version of the assembly
from disk (from the GAC), even though the application is configured
to run on .NET 4.0. The workaround is to remove a couple of web.config
elements, so that ASP.NET will load the correct version of those
assemblies at startup.

Work Item: 17728

--HG--
branch : 1.x
This commit is contained in:
Renaud Paquay
2011-06-09 09:07:41 -07:00
parent 3bcbcb4f04
commit 340c2bdbc2

View File

@@ -63,8 +63,6 @@
<add assembly="System.Web.Abstractions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL"/>
<add assembly="System.Web.Routing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL"/>
<add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<remove assembly="mscorlib" />
<remove assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<remove assembly="System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<remove assembly="System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<remove assembly="System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />