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...Getting StartedGetting StartedWarnings in DNN 5.1Warnings in DNN 5.1
Previous
 
Next
New Post
1/25/2010 4:30 PM
 
Hi all,

I'm using DNN 5.1; at compile time I get the following warns:

'DotNetNuke.Entities.Users.UserMembership.Username' is obsolete: 'Deprecated in DNN 5.1' - but nothisn more said; if it's deprecated, which one should I use?

'DotNetNuke.Entities.Users.UserController.GetUser(int, int, bool)' is obsolete: 'Deprecated in DNN 5.1. Not needed any longer for due to autohydration' it is used as:
DotNetNuke.Entities.Users.UserInfo objUserInfo = DotNetNuke.Entities.Users.UserController.GetUser(0, userid, false);
should I replace with:
DotNetNuke.Entities.Users.UserInfo objUserInfo = DotNetNuke.Entities.Users.UserController.GetUserById(0, userid);
?

Thanks in advance,
Lucian
 
New Post
1/25/2010 6:55 PM
 

the properties are only set with obsolete warnings, so the code still works, so if you examine what the code does you'll see what should be used i.e. the obsolete code redirects to the new API methods  - in this case you see

Return

_User.Username

which resolves to userinfo.username

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/12/2010 4:13 PM
 
Sure it still works, but the developer shouldn't have to examine the source code.  When applicable, an Obsolete attribute's description must indicate the property that has replaced the obsolete property.
 
New Post
7/13/2010 2:47 AM
 
There are a lot of ways that the source code and project is being worked on to better document things like this Matt. In the future you will definitely find better results

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/24/2013 4:54 AM
 

If it is so simple as to look into the code, then why are there in 7.07 still calls that are deprecated since 5.0. Anno 2013 I'm still waiting for that 'future with better results'.

I'm currently looking for the replacement of a deprecated call (UserMembership() ), but all I can find is topics like this one.

The good news is that there is an  a list of obsolete methods that require hints to new API calls. The bad news is that it is being postponed over and over again.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedWarnings in DNN 5.1Warnings in DNN 5.1


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