Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If the <code>compilation</code> element in your web.config file has the <code>targetFramework="4.0"</code> attribute, I don't think the references to the System.Web.Extensions assembly are required anymore. If you look at the root-level web.config file at <code>%WINDIR%\Microsoft.NET\Framework\v4.0.30319\Config</code>, you will notice that the following lines are already in the <code>&lt;controls&gt;</code> section of the web.config file:</p> <pre><code>&lt;add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/&gt; &lt;add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/&gt; &lt;add tagPrefix="asp" namespace="System.Web.UI.WebControls.Expressions" assembly="System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/&gt; </code></pre> <p>The System.Web.Extensions assembly is also referenced in the <code>&lt;compilation&gt;&lt;assemblies&gt;</code> section</p> <pre><code>&lt;add assembly="System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /&gt; </code></pre> <p>and the following <code>&lt;httpHandlers&gt;</code> are added as well</p> <pre><code>&lt;add verb="*" path="*_AppService.axd" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="False" /&gt; &lt;add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="False"/&gt; &lt;add path="*.asmx" verb="*" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="False" /&gt; </code></pre> <p>Additionally, the following <code>&lt;httpModules&gt;</code> are registered by default</p> <pre><code>&lt;add name="ScriptModule-4.0" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/&gt; </code></pre> <p>In short, your web.config file probably should not contain any references to the System.Web.Extensions assembly because it is already referenced in almost every conceivable way in the root-level web.config file.</p> <p>Additional References: <a href="http://msdn.microsoft.com/en-us/library/dd483478.aspx" rel="noreferrer">How to: Upgrade an ASP.NET Web Application to ASP.NET 4</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload