<Runtime>
<AssemblyBinding xmlns = "urn: schemas-microsoft-com: asm. v1">
<DependentAssembly>
<AssemblyIdentity name = "System. Web. Extensions" publicKeyToken = "31bf3856ad364e35"/>
<BindingRedirect oldVersion = "1.0.0.0-1.1.0.0" newVersion = "3.5.0.0"/>
</DependentAssembly>
<DependentAssembly>
<AssemblyIdentity name = "System. Web. Extensions. Design" publicKeyToken = "31bf3856ad364e35"/>
<BindingRedirect oldVersion = "1.0.0.0-1.1.0.0" newVersion = "3.5.0.0"/>
</DependentAssembly>
</AssemblyBinding>
</Runtime>
I helped my friends publish a website a few days ago. A page with a city choice was refreshed with Microsoft's updatepanel. However, when published to the Internet, there will be no refreshing effect. It was strange that later I changed the Extensions version in the configuration file to 1.0.61025.0.
Web. Config Configuration
1 2 <remove verb = "*" path = "*. asmx"/>
3 <add verb = "*" path = "*. asmx "validate =" false "type =" System. web. script. services. scriptHandlerFactory, System. web. extensions, Version = 1.0.61025.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35 "/>
4 <add verb = "*" path = "* _ AppService. axd "validate =" false "type =" System. web. script. services. scriptHandlerFactory, System. web. extensions, Version = 1.0.61025.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35 "/>
5 <add verb = "GET, HEAD" path = "ScriptResource. axd "type =" System. web. handlers. scriptResourceHandler, System. web. extensions, Version = 1.0.61025.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35 "validate =" false "/>
6 7
8 <modules>
9 <remove name = "ScriptModule"/>
10 <add name = "ScriptModule" preCondition = "managedHandler" type = "System. web. handlers. scriptModule, System. web. extensions, Version = 1.0.61025.0, Culture = neutral, PublicKeyToken = 31BF3856AD364E35 "/>
11 </modules>
12
It is very difficult for Microsoft to add bindingRedirect to the. config configuration file, so that it can change the version number to another version number during program loading. I finally figured out why there was no assembly in version 3.5.0.0. It is estimated that Microsoft is trying to mark this release as framework3.5.