This is one thread in a series announcing various "breaking changes" in the next version of DotNetNuke. Please limit discussion in this thread to understanding, impacts and workarounds related to this specific change.

* Disclaimer *
The DotNetNuke Team is dedicated to making every effort to minimize impacts to module developers (many of us are module developers ourselves). However for this release introduction of the MS Membership & Roles Provider makes introduction of breaking changes impossible to avoid (see Breaking Change #1, view post 713322). In order to make best use of an unfortunate situation, the DNN team will implement additional breaking changes so that their impact will be minimized for future releases. We apologize for the inevitable inconvenience this will cause. Please note that all "breaking changes" announcements will appear in the Core Framework forum (view forum 97).

---

Change Name: Reorganization of Namespaces
Logged by: bigwebmaster (Dan Caron)
Area of Impact: All classes in root DotNetNuke namespace and most other classes elsewhere.
Impacted DNN Versions: All modules released on versions prior to 3.0
Who is Impacted: Developers, Organizations with custom modules
Short Description: Any module utilizing classes directly under the DotNetNuke namespace and many other classes under other namespaces, will throw exceptions due to the namespace reorganization. Projects will also not compile until namespaces have been aligned with the new DotNetNuke namespaces.
Full Description: Currently DotNetNuke's namespace structure is very flat, and structure loosely enforced. All classes in the root of DotNetNuke will be moved into a hierarchical namespace structure.
Workaround or Recommended Course of Action: Documenttion of DotNetNuke's new namespace structure will be released advance (soon) so developers can search & replace or rename the references to DotNetNuke namespaces.

Scott,

Giving the breadth and width of all these breaking changes I cannot help but think it is now mandatory that nightly builds of 3.0 be made available publicly so that developers can begin remediation steps now. Most software companies do this for major development partners and some do it for all registered users as part of the "PARTNERSHIP" that is necessary between the Core Team (Inner and Outer), major contributors, and developers.

What can be done to atleast get some minimal builds of "alpha" version of DNN 3.0 so we can all get on the ball. Most folks I talk to want to be pro-active and not reactive. Reactive management of time and resources is terribly inefficient and contrary to most business models.

I appreciate your thoughts Scott.

Cheers

Tom ~

We've been missing your participation... welcome back! Please respond in the core team forums to the program we have proposed specifically to help address this problem. We could use your feedback there and your assistance as well.

Cheers,
Scott

OK Tom... MY BAD! Looks like you've actually retired from the core team... I was just missing you *grin*. The logo threw me...

Hang with us a couple of days... we really are trying to do something to help here and it'll be public by Monday.

Nice to see you around!

Cheers,
Scott

Yeah! ;)

Scott Mcculloch can probably fill you in the some of my happenings or I can talk offline via email regarding that.

Love the work that is being done though and please understand I am in favor of the breaking changes as these were items we were trying to address back when I was in the core as well. It is nice to see them coming along.

Cheers.

FYI: All modules will need to inherit the following: DotNetNuke.Entities.Modules.PortalModuleBase

Scott,

What exactly will be

<quote> public by Monday </quote>

Will there be an alpha release?

Thanks

mrswoop wrote:

Workaround or Recommended Course of Action: Documenttion of DotNetNuke's new namespace structure will be released advance (soon) so developers can search & replace or rename the references to DotNetNuke namespaces.

Hi Scott.

Was this document ever released?

Cheers
Dave

mrswoop wrote:

Workaround or Recommended Course of Action: Documenttion of DotNetNuke's new namespace structure will be released advance (soon) so developers can search & replace or rename the references to DotNetNuke namespaces.

I'm trying to upgrade a V2.x module that uses
<code>Dim _portalSettings As PortalSettings = CType(HttpContext.Current.Items("PortalSettings"), PortalSettings)</code>
in the Page_Load.

Is there a recommended replacement?
Thanks

The following will work Sam

Dim _portalSettings As DotNetNuke.Entities.Portals.PortalSettings = CType(HttpContext.Current.Items("PortalSettings"), DotNetNuke.Entities.Portals.PortalSettings)

Or add an "Imports DotNetNuke.Entities.Portals" to the top of your .vb page.