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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Usage of existing DNN API has to be customized?Usage of existing DNN API has to be customized?
Previous
 
Next
New Post
4/18/2010 5:48 AM
 

I recently upgraded my application from 4.9 to 5.3. For getting more/better info regarding users some of my custom created classes utilize some DNN API like SkinController class to access GetSkin method. This was working fine in 4.9 but in 5th version I started getting errors for such classes like : 'GetSkin' is not a member of 'DotNetNuke.UI.Skins.SkinController'

Issue is not with the code written in DNN default controls but with cases like me who have to use various classes present under DotNetNuke dll in custom classes.

This is just an example, I'm not sure if DNN has updated any other of its public class as well.  For upgrading I have to update their use in my code as well. Can I find information somewhere about all such 'updated' clsses by DNN developers? It will be of great help for me.

 
New Post
4/18/2010 3:45 PM
 

I am not aware of anywhere that tracks updated 'API' changes to give you what you need. 


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
4/19/2010 1:40 AM
 

Thanks for the reply. I'll handle all such changes. But in that case for errors like: 'GetSkin' is not a member of 'DotNetNuke.UI.Skins.SkinController' how should I determine/analyze which new class should my code refer to? Is this available as part of tooltip provided in build error/code as per old version or I have to go through XML descriptions of new classes/methods to understand changes required?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Usage of existing DNN API has to be customized?Usage of existing DNN API has to be customized?


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