Member Avatar for diya0076

hi i download ajax tool kit..3.0.30512.1
n also installed .net framework 3.5
n i add the dll file into my project bt when i drop any of the control of ajax it shows the following error:

Error 1 Assembly 'AjaxControlToolkit, Version=3.0.30512.20315, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' uses 'System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'


what to do..?

  • 3 Contributors
  • 7 Replies
  • 194 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by sknake

Dani AI

Generated

Short summary and practical fixes — this thread shows two separate but related problems: a framework/version mismatch and the runtime requirement for an AJAX ScriptManager. As advised, the build your page uses must match the AjaxControlToolkit build; as pointed out, web.config entries can also force an old ASP.NET AJAX assembly. The new Ajax‑enabled site worked because it already had the correct web.config plus a ScriptManager on the pages.

Steps to resolve (apply in this order):

  1. Retarget the project to .NET Framework 3.5 (Project → Properties → Target Framework for a Web Application; use Property Pages for a Web Site).
  2. In Solution Explorer → References, remove any old System.Web.Extensions reference and add the System.Web.Extensions from the 3.5 assemblies. Delete any stray System.Web.Extensions.dll from the bin folder. Clean and rebuild.
  3. Remove or update any explicit web.config entries that reference the older ASP.NET AJAX assembly so they no longer force the 1.0 runtime. If you prefer a redirect instead of removing entries, add a binding redirect in web.config like this:
<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" culture="neutral" />
      <bindingRedirect oldVersion="1.0.0.0-3.5.0.0" newVersion="3.5.0.0" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>
  1. Fix the runtime error by placing a ScriptManager (or the toolkit’s ToolkitScriptManager) on the page or in the Master Page so all pages get it:
<asp:ScriptManager ID="ScriptManager1" runat="server" />

or

<ajaxToolkit:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server" />

Extra tips: compare your web.config to the one in a fresh Ajax‑enabled site to copy missing sections, restart Visual Studio after changes, and ensure the deployment server has .NET 3.5 installed.

Recommended Answers

All 7 Replies

Member Avatar for sknake

It looks like your project is set up using the .NET framework 1.1 and not the 3.5 framework. If you convert your project to a 3.5 application it should work

Member Avatar for Ramesh S

Solution 1. If you have entiries like <add assembly="System.Web.Extensions, Version=1.0.61025 ..../> and System.Web.Extensions, Version=3.5.0.0..../> in your web.config(under <assemblies> section), remove the first one.

Solution 2. If you only have assembly entry for version 1.0.61025 in web.config, then change it to version accordingly.

Also you need to check whether this assembly exists in your GAC.


If the above solutions do not solve your problem, post the details under <assemblies> section from your web.config.

Member Avatar for diya0076

hey thanx by adding
<add assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

in web.config it works

bt now it throws run time exception ::?:

InvalidOperationException
A ScriptManager is required on the page to use ASP.NET AJAX Script Components.

Member Avatar for diya0076

hey when i create new website that is ajax enabled then this error is gone...

so what changes i have to made in my project which is not ajax enabled?

Member Avatar for sknake

Probably the framework you're compiling against that i stated in my first post. But since you seemed to ignore that I don't know why i'm answering again.

It looks like your project is set up using the .NET framework 1.1 and not the 3.5 framework. If you convert your project to a 3.5 application it should work

Member Avatar for diya0076

how to set the project to use the different framework?

Member Avatar for sknake

Right click on the project in your solution explorer and select "Properties". Under the "Application" section you will see "Target Framework." Select "3.x" and away you go.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.