abdu bukres
Top achievements
Rank 1
Rank 1
abdu bukres
asked on 09 Nov 2009, 09:09 PM
I am using DotNetNuke with version fromn 2009 Q1. I have a third party DNN module which is giving the error below. DNN can only use one version of the assembly. Is there a way to make a DNN module use the newer Telerik assembly without recompiling the module?
Error Message:
Could not load file or assembly 'Telerik.Web.UI, Version=2008.3.1125.20, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Error Message:
Could not load file or assembly 'Telerik.Web.UI, Version=2008.3.1125.20, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
2 Answers, 1 is accepted
0
Schlurk
Top achievements
Rank 2
Rank 2
answered on 11 Nov 2009, 06:20 PM
I read somewhere in the forum that in order to do this you would have to have access to the source code (licensed developer) and re-compile the assemblies under a different name in order to prevent conflicts.
0
Hello Abdu,
The .NET framework does not allow you to use two different versions for the same assembly in a single web-application. The reasons are several: the assembly names are the same, so there is no way to keep them both in the same folder; the namespaces are the same, which in turn does not allow you to use different assemblies on the same page or project.
In difference to dotnetnuke.dll, Telerik's assemblies are Strong-Named, thus you cannot separate your code form the assembly code. I'm afraid there's not much we can do on the matter. I can tell one thing for sure - we cannot ship not Strongly-Named assembly. The only reasonable solution for this case is the 3rd party module vendors to always update their modules to work with the latest version of Telerik.Web.UI.dll.
Best wishes,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
The .NET framework does not allow you to use two different versions for the same assembly in a single web-application. The reasons are several: the assembly names are the same, so there is no way to keep them both in the same folder; the namespaces are the same, which in turn does not allow you to use different assemblies on the same page or project.
In difference to dotnetnuke.dll, Telerik's assemblies are Strong-Named, thus you cannot separate your code form the assembly code. I'm afraid there's not much we can do on the matter. I can tell one thing for sure - we cannot ship not Strongly-Named assembly. The only reasonable solution for this case is the 3rd party module vendors to always update their modules to work with the latest version of Telerik.Web.UI.dll.
Best wishes,
Paul
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.