This is a migrated thread and some comments may be shown as answers.

Weird problem with System.Web.Extension version

2 Answers 362 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Francisco asked on 01 Nov 2016, 02:10 AM

Hi, I'm modifying an old VS project, it uses .net 2.0 and I normally add my telerik RadComboBox and there is no problems...

The thing is that in a different PC, there is an error, the other PC has the same telerik version and the same visual studio version, this is the error:

Assembly 'Telerik.Web.UI, Version=2016.2.607.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4' uses 'System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Then I researched and I realized about the project being in the past in .net 2.0 and I guess that for the future all references to old System.Web.Extensions and lower .net should be replaced with newer versions, but the thing is that I don't get why in my PC i don't get the error and in other PCs the error is there even if I add the telerik control in those PCs, i.e., if I go with the project to other PC and add the telerik RadComboBox there, I get the error anyway...

I'ts kind of weird, please any help or at least some explanation.

Thanks in advance.

2 Answers, 1 is accepted

answered on 01 Nov 2016, 08:20 AM

Hello Francisco,

My best guess is that the second machine does not have .NET 4.0 installed so it only has the old versions of the WebExtesnsions assembly. The alternative is that there is an issue with the GAC on the second machine and only the old version is available. In either case, installing or repairing .NET should solve the issue. An alternative would be to add a bindingRedirect entry so the new version of the assembly is fetched. A third possibility is that there is something peculiar on your own machine that allows the project to work and reference the correct version.

Generally, I would advise that you upgrade your project fully so it targets .NET 4.0 properly instead of relying on bindingRedirect entries or flukes in order to work. This will ensure proper assembly references that should resolve without issues on any machine.

Regards,

Marin Bratanov
Telerik by Progress

Check out the new UI for ASP.NET Core, the most complete UI suite for ASP.NET Core development on the market, with 60+ tried-and-tested widgets, based on Kendo UI.