Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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...Building ExtensionsBuilding ExtensionsModulesModulesTelerik conflict questionTelerik conflict question
Previous
 
Next
New Post
7/15/2010 6:25 AM
 
Hello,

Some months ago, i created a module that i now want to put on Snowcovered. But i'm stuck with the use of Telerik.

The module has a reference to Telerik. in Visual Studio, the reference property "specific version" is set to "false", which means according to me that it should work with every Telerikversion in the DNN's bin folder. But every time i have another Telerik version installed, DNN throws the error that de referenced version is not the same as the installed version of DNN.

As solutions for my projects, i modified the web.Config and added a dependent assembly rule, and this works fine. Now that i want to sell the module on Snowcovered, i don't want this solution anymore because noobs are mostly unable to do this.
Since Telerik 5.2 came out, Telerik is included in Dotnetnuke, it must be possible to use the default Telerik dll that is included in DNN. But i will have the same problems with the reference.

The included wrapperclasses in Dotnetnuke aren't complete enough to use for me (i miss the wrapper for RadTreeNode & DateTimePicker



So, what are your suggested options to solve the problem?
 
New Post
7/16/2010 3:49 AM
 
Rubinho, the DNN OEM agreement with Telerik requires you to access the Telerik controls via the DNN wrappers. If your module only targets DNN5.2+ (the first version that had the RAD controls bundled I believe), the simplest approach is to do just that, and you are guaranteed to have 2009.3.1103 or later of the RAD controls available.

However, there are disadvantages, as the DNN wrappers are not yet complete, and do not include design-time support, so you have to set your controls up in code-view.

On the other hand, if you have your own RAD Controls licence, you have other options. Firstly you can develop against your own licenced version, and exclude it from the module when packaging it. If your version is older than the one shipped with your target DNN installation, that should work OK, so long as Telerik have got their backwards-compatibility right. On the other hand, I wouldn't develop against a version newer than the one that ships with DNN, as you may use features not yet available to DNN.

The other option you have if your licence gives you access to the source code, is to ship a protected version of the RAD controls dll that only works with your application. Telerik will allow you to do that. The instructions on how to do this are here: http://www.telerik.com/help/aspnet-ajax/protecting-telerik-asp.net-ajax-assembly.html

Hope that helps.


Paul Taylor
Dotcom Software Solutions Ltd
DotNetNuke, ASP.NET and SQL Server Development
 
New Post
7/16/2010 7:31 AM
 
Thank you Paul for the detailed information

I'm considering of doing the last option, because we have the full Telerik license.

Thanks
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesTelerik conflict questionTelerik conflict question


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out