I'm developing a module that will need store two or three pieces of information specific to a user.  What is the "DNN way" to do this?

I'm not sure how Michael does it, but a Module can create its own "Profile" properties, and make them Invisible so it can manage them behind the scenes.

---

Charles Nurse Chief Architect Evoq Content Team Lead, DNN Corp. Want to contribute to the Platform project? - See here

MVP (ASP.NET) and ASPInsiders Member

There’s nothing wrong with adding your own table to store these properties.

DNN profile properties are defined on a per/portal basis. Modules are defined on a per/host basis. If a user is a member of multiple portals, their data will be replicated in each portal. Speaking of this, does anyone know how to add a profile property definition tied to a module? Do you have to check whether the property is defined for the portal in each module instance?

---

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.