Download packages updated April 27, 2017 to resolve issues related to dilated convolution on Kepler Architecture GPUs. CuDNN User Guide. CuDNN Install Guide. CuDNN v6.0 Library for Linux. CuDNN v6.0 Library for Power8. CuDNN v6.0 Library for Windows 7. CuDNN v6.0 Library for Windows 10. CuDNN v6.0 Library for OSX. CuDNN v6.0 Release Notes. The DNN Platform has been downloaded more than 8 million times and powers more than 750,000 websites globally. A community of more than 1 million members forms a powerful support network. Thousands of free and commercial extensions, apps and skins are available at the DNN Store that make extending a DNN site fast and affordable.
There is uncertainty surrounding the use of DNNRadMenu in the community edition of DotNetNuke.
It is my understanding that as of DNN 5.6.2, it is OK for community edition users to use (and modify) the DNNRadMenu wrapper, but these users/developers will not have access to the core telerik code (which is bundled into an enormous DLL that ships with all versions of DNN).
DNN RadMenu is obtained here:http://dnnradmenu.codeplex.com/
From the DNN / Telerik partnership Q&Ahttp://www.telerik.com/purchase/faqs/telerik-dnn-partnership-qanda.aspx
DotNetNuke Community Edition users will be able to develop using RadControls through standard user interface extensions provided in the DotNetNuke platform. Community Edition developers will have more limited access to the Telerik RadControls than Professional Edition developers and will not have full developer license rights to use the Telerik RadControls toolset. Community Edition developers will only be able to develop though standard user interface extensions provided with the core platform.
Can community edition users freely deploy the DNN RadMenu (within DNN installations)?
My interpretation is that we can tweak the DNN RadMenu SkinObject all we want, but we will not have access to the core telerik code. I know there is a strong desire (from DNN Corp) for shops like mine to subscribe to DNN Pro or Enterprise, but sometimes that is just not in the budget for a particular project. I feel like part of the reason for this partnership is to give access to these controls, like DNNRadMenu, to community edition clients so as to increase the pervasiveness of the controls... which ought to increase sales for licenses for greater access to the controls. If I am correct with these assumptions, then I would like to take advantage of the opportuntiy.
closed as off-topic by JasonMArcher, Infinite Recursion, gunr2171, rene, SamJun 19 '15 at 19:48
- This question does not appear to be about programming within the scope defined in the help center.
2 Answers
Dnn Version 5. 6 Download Pc
Can community edition users freely deploy the DNN RadMenu (within DNN installations)?
Yep - any Telerik stuff that is wrapped by DNN can be used in a Community Edition installation.
Ian RobinsonIan Robinson
Is the DNN RadMenu project 'wrapped by DNN,' or is it a third party component that is not associated with DNN corp? My understanding is that 'wrappers' only refers to the types in DotNetNuke.Web.UI
Under the current licensing, you cannot modify the dnnradmenu or any of the other skin objects (I posted) because they are not using the core Telerik wrappers (unless you are a PE/EE customer or have a valid Telerik license). They currently do not use the wrappers because as of dnn 5.6.2 they didn't exist. Once 6.0 is a public release (not CTP/Beta), this will change and I will update all the skin objects to use the new wrappers and then anyone can modify the skin objects without licensing concerns.
Dnn Platform Download
Also, as an FYI, the DDR Menu will be the new default navigation in 6.0 (not the current DNN Menu or a Telerik alternative).