New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedTelerik Controls Version ProblemTelerik Controls Version Problem
Previous
 
Next
New Post
1/12/2011 9:28 AM
 
Hi, I am cross posting this from the Telerik forum as per thier suggestion.   We have been trying to resolve or at least understand a version problem for over a week and have been unsuccessful. 

In short I have purchased and install V3 of the controls yet DNN keeps trying to load V2.  I have a  work around but would really like understand why this is happening and if I should not have installed the new version of the controls.  Its my intent to use other products, like reporting, from Telerik and need to have them installed.  Any guidance would be appreciated.

The full discussion is here.

http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/version-problem.aspx#1484917

----------

I am having one heck of a time with versions of Telerik.Web.UI.  I Telerik Ajax controls v2010.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.

  <runtime>

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

      <dependentAssembly>

        <assemblyIdentity name="TeHi 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 teamlerik.Web.UI" publicKeyToken="121fae78165ba3d4" />

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

-------



 
New Post
1/12/2011 12:28 PM
 
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
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/12/2011 12:40 PM
 
Brian, that's a big help and I understand it now.  Thanks.   Would I be correct in saying that the V2 request is embedded  somewhere in the DNN binaries?
 
New Post
1/12/2011 12:54 PM
 
Yes, any assembly that references Telerik.Web.UI (whether DotNetNuke.Web or a 3rd party module) will include the version number with that reference (because Telerik.Web.UI is strong-named, regardless of setting the Specific Version property of that reference to False in Visual Studio).  It isn't possible for a .NET assembly to reference a strong-named assembly without regard to version.

Hope that helps,

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/12/2011 12:59 PM
 
Got it.  Thanks for a such a good explanation. 
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedTelerik Controls Version ProblemTelerik Controls Version Problem


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.