Version Problem

[Ed]

I am having one heck of a time with versions of Telerik.Web.UI.  I had installed versions from 1 on and auto updated to 2010.3.  My page complains that it can not locate version 2010.2.929.35  yet 2010.03.1215.35 is installed.  I've had to add a bindingredirect to my web.config.  Is this normal?

  <runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <dependentAssembly>

        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />

        <bindingRedirect oldVersion="2010.2.929.35" newVersion="2010.03.1215.35" xmlns="urn:schemas-microsoft-com:asm.v1" />

[Bodevain Svensson]

To be on the safe side, it is recommended to use bindingRedirects, at least this is what I found explained in the fifth bullet under the Support category on this page. Provided that all the Telerik dll references point to the new version in your DNN site, you won't need binding redirects in web.config.

[Ed]

Even with the reference pointing to the project's Telerik DLL in the DNN bin folder it still tries to load an older version.  I can't figure out where the reference to the old DLL is coming from.  I've uninstalled and reinstalled the controls to no avail.  I'd prefer to not have to change the web.config each time a new DLL is upgraded.

[sitefinitysteve]

I gotta say Ed, to be honest, the 3 seconds it takes to update the web.config after an upgrade are more than worth it when you consider the headaches you're running into now. :)

I've got a suggestion in for the VS Extension team to update assembly bindings during an update via their wizard...not sure if that is\was implemented yet though

[Erjan Gavalji]

Hi guys,

@Bodevain, @Steve, thanks for the help! The BindingRedirect addition is in our Product Backlog for Q1 2011 release with a high priority. I hope we won't meet any obstacles with the implementation.

@Ed, you could basically update the reference in your project and rebuild it so that it now refers the latest version. You would need to do a re-reference and a rebuild each time you update RadControls if you prefer not modifying the web.config. You would need to remove the <AssemblyBinding> section for the Telerik.Web.UI assembly from your web.config as well.

Still, I agree with Steve that this is the harder approach than modifying the BindingRedirect. It is just the .NET assembly reference rules that define either a rebuild or a BindingRedirect to exist.

Kind regards,
Erjan Gavalji
the Telerik team

[Ed]

Thanks for the help everyone.  The problem I have is I don't understand why its happening.  The workaround is fine, I can document it in the upgrade instructions. 

But what I am building now is brand new and my understanding is this should not be an issue.  I have uninstalled, removed references, installed again, referenced and re-referenced, browsed for the right DLL in my project and referenced, created new a new project, upgraded via the upgrade wizard, tried to clear temp .NET files, etc.

I don't know where or why the page is requiring v2 instead of the referenced and installed v3.  I've done a text and DLL search on my entire system, including the registry, and v2 is not referenced.  As far I can tell V2 doesn't exist on the system so why is it being requested?
 

[Erjan Gavalji]

Hi Ed,

I guess it is a class library project that is still holding a reference to a local copy of the older Telerik.Web.UI assembly version. Though not sure of the name, the default DotNetNuke solution contains a ClassLibrary, which references the Telerik.Web.UI assembly. I guess your main WebApplication project holds a reference to the newer RadControls assembly.

What happens during rebuild is that the IDE builds the control library and copies all its references to the WebApplicationProject's bin. It recompiles the WebApplication project too. Depending on the CopyLocal property of the reference (and possibly other properties too), it either replaces the assembly in the BIN with the latest one, or it leaves the older one.
In both cases, it would be either the assembly of the ClassLibrary project, or the main WebApplication project, which will throw an exception for not being able to find the assembly it needs.

Having these said, can you check the other projects in the solution for a reference to the Telerik.Web.UI assembly?

Cheers,
Erjan Gavalji
the Telerik team

[Ed]

I have 3 projects all reference the same and correct version.  They all have:

Aliases = global
copy local = true.
version = 2010.3.1215.35
runtime version = v2.0.50727

The last project created yesterday after a reinstall references: C:\Dev\GMM\Dev\DNNDev\bin\Telerik.Web.UI.dll  with specific version = true

The other 2 projects reference: C:\Users\ed\AppData\Roaming\Telerik\Updates\Telerik.Web.UI_2010_3_1215_Dev_hotfix\Bin35\Telerik.Web.UI.dll

Interestingly enough these 2 have specific version = false.

Chaning all project referneces to specific version = true and C:\Dev\GMM\Dev\DNNDev\bin\Telerik.Web.UI.dll did not solve the problem.

Another interesting note is when I add a refernece to the project and navigate to the .NET tab, the Telerik Web UI dll does not show up in the list, I have to browse for the DLL in the DNN\bin folder and the Telerik assemblys (reporting) that do show up in the list are all v2.0.50727.

[Erjan Gavalji]

Hi Ed,

That's strange indeed...

Just to make sure we're on the same path: 2.0.50727 is the version of .NET Framework 2.0, could it be that you checked that for the Telerik Reporting instead?

Anyways, the Telerik.Web.UI assembly is intentionally not listed in the Add Reference dialog of Visual Studio. This is because of some toolbox drag-and-drop problems and design time errors.

Can you check the GAC for the existence of an older Telerik.Web.UI assembly? It could be that the .NET runtime finds the older Telerik.Web.UI assembly in the GAC and loads it instead...

By the way, I assume you have the <assemblyBinding> node, pointing to the older Telerik.Web.UI assembly commented/removed from your web.config. Is it?

Kind regards,
Erjan Gavalji
the Telerik team

[Ed]

Hi Erjan, Telerik.Web.UI.dll is not in C:\Windows\assembly. However there are versions of it as listed below.  It looks like the assembly binding is correct.  My projects are set to compile with .Net 3.5 and I'm running 64 bit Win7 Pro.

------

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="bin;bin\HttpModules;bin\Providers;bin\Modules;bin\Support;" />
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.5.0 - Date: 10/28/2010 12:12:44 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.5.0 - Date: 10/28/2010 1:54:28 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.6.0 - Date: 11/24/2010 7:54:04 AM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <bindingRedirect oldVersion="2010.2.929.35" newVersion="2010.03.1215.35" xmlns="urn:schemas-microsoft-com:asm.v1" />
      </dependentAssembly>

-----------------


C:\Windows\Microsoft.NET>dir telerik.web.ui.* /s
 Volume in drive C is OS
 Volume Serial Number is 12A8-4DA4

 Directory of C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\dnndev\05844808\82ad7e2e\assembly\dl3\08feca60\00f0307f_c49bcb01

01/06/2011  12:08 PM        18,436,096 Telerik.Web.UI.DLL
               1 File(s)     18,436,096 bytes

 Directory of C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\dnndev\864ec850\45268781\assembly\dl3\406aa5f5\00b469c2_2f5fcb01

12/30/2010  11:49 AM        17,186,304 Telerik.Web.UI.DLL
               1 File(s)     17,186,304 bytes

 Directory of C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\dnndev\9a414329\c124539b\assembly\dl3\4cae5d06\00f0307f_c49bcb01

01/07/2011  12:12 PM        18,436,096 Telerik.Web.UI.DLL
               1 File(s)     18,436,096 bytes

 Directory of C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7077a231\a855cbbd\assembly\dl3\538e889f\00f0307f_c49bcb01

01/06/2011  09:19 AM        18,436,096 Telerik.Web.UI.DLL
               1 File(s)     18,436,096 bytes

 Directory of C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\dnndev\66a5ea43\45268781\assembly\dl3\8c83561f\00f0307f_c49bcb01

01/07/2011  01:29 PM        18,436,096 Telerik.Web.UI.DLL
               1 File(s)     18,436,096 bytes

     Total Files Listed:
               5 File(s)     90,930,688 bytes
               0 Dir(s)  371,098,058,752 bytes free

C:\Windows\Microsoft.NET>

[Erjan Gavalji]

Hi Ed,

The other occurrences of the Telerik.Web.UI assembly are cached by the .NET Framework.
Can you try cleaning the Temporary ASP.NET Files folder?
To do that, please, close all Visual Studio instances first and perform an iisreset (to close all the applications that might use the temporary ASP.NET files).
Then, start a Windows Explorer and navigate to C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

You can safely delete all the folders/files there. The deletion will only cause a slight slowdown the first time you load/start another web project.

Kind regards,
Erjan Gavalji
the Telerik team

[Ed]

Erjan, I found 6 instances of the DLL in Microsoft.NET., deleted them all, commented out the binding redirect but still have the same problem.

Note: dnndev is my IIS virtual folder

The error is:

 Parser Error Message: Could not load file or assembly 'Telerik.Web.UI, Version=2010.2.929.35, 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)

I did find 1 DLLthat was V2 in:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\dnndev\864ec850\45268781\assembly\dl3\406aa5f5\00b469c2_2f5fcb01

After deleting all the DLLs and rebuilding the project and testing the DLLs showed up.  All are V3.

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\dnndev\66a5ea43\45268781\assembly\dl3\8c83561f\00f0307f_c49bcb01

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\dnndev\9a414329\c124539b\assembly\dl3\4cae5d06\00f0307f_c49bcb01

[Lini]

Hi Ed,

Perhaps you should post your question on the DNN forums as well. The RadControls assembly (Telerik.Web.UI) is used extensively in the DNN code and each DotNetNuke version ships with a specific version of our controls. I don't think that upgrading only the Telerik controls is possible without also upgrading the DNN version as well. Since the current DNN version (5.6.0) references the 2010.2.929.35 build of Telerik.Web.UI, you should not try to upgrade the controls to a new build (e.g. Q3 2010). Instead, you should wait for DNN Corp to release an new version, which will feature the updated controls as well.

While upgrading just Telerik.Web.UI is theoretically possible, you might break some vital part of the DNN site - e.g. the admin panel or the page navigation due to some change from the Q2 to Q3 releases of RadControl. This is why I strongly suggest that you go to the DNN forums. I am sorry that we were not able to help you with your problem.

All the best,
Lini
the Telerik team

[Ed]

I see.  I will post there.  One problem with not upgrading is I’ve purchased the Telerik controls so I can use what DNN doesn’t supply mostly including Reporting. 

[Ed]

 Lini, your suggestion to check DNN was spot on.   Thanks.  I have an answer. The binding redirect is the proper way to handle this.

http://www.dotnetnuke.com/Resources/Forums/tabid/795/forumid/201/postid/403408/scope/posts/Default.aspx#403408

Here's the post from Brian Dukes:

Because Telerik.Web.UI is strongly-named, referring to new versions with code that was compiled against the old version requires that bindingRedirect in the web.config.  That web.config element is going to be the final say on which version should be used.  So, your solution isn't really a workaround, but the only way around the issue (if you weren't using that, the DNN core (not to mention any extensions using Telerik) would be the ones giving you errors.

In terms of whether it's an acceptable change to make, I would say that it's a medium level of safety.  If you need to do it (if there's something in the newer version of Telerik that you're using) then go ahead.  If you can avoid it, go ahead and use the version that comes with DNN.  As they said on the Telerik forum, there's a possibility of changes breaking something in DNN, but in actuality there's a fairly low probability of that being an issue.

Hope that helps,

---

Brian Dukes Engage Software St. Louis, MO 314.966.4000