Learn More





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

HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtDetails?Details?
New Post
1/11/2015 9:58 PM

So what are we talking about here, a complete ground up rewrite?

Backwards compatibility?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee Software Solutions DotNetNuke Module Development, Upgrades and consulting. a chat room for DotNetNuke discussions
New Post
1/12/2015 7:32 AM

No.  Not a ground up rewrite.  We need to keep many of the features and functionality that already exists. But everything in DNN today won't run on ASP.Net 5 (which is MVC only)  so we have to identify those parts that don't run and rebuild them.  We'll also take the time to revisit some outdated bits of the platform and either remove or update them using more modern approaches.

The point of this forum is to start having the conversations about what we should keep and what we shouldn't.  These conversations should be in the open rather than just limiting it to the MVP group or other private channels. The goal is to get participation from a much broader part of our community.

Joe Brinkman
DNN Corp.
New Post
1/17/2015 12:02 PM
ASP.NET 5 supports WebForms. You have to use the the full CLR. WebForms won't run in cloud optimized runtime. I am not saying this proposing to stick with WebForms. WebForms is a legacy technology.
New Post
1/17/2015 1:21 PM

Technically you can say that ASP.Net 5 does include the full .Net stack, including support for Web Forms.  However, the core .Net stack is the only one that is Open Source, cross platform and which uses the new Nuget based deployment model.  Full stack .Net is there for Winforms, WPF, and ASP.Net backwards compatibility support, but in no way addresses many of the shortcomings of the current ASP.Net stack.

Microsoft recognizes that in order to truly address these issues, they needed to rebuild ASP.Net and the .Net stack.  If a DNN customer wants to take advantage of the benefits offered by the core CLR stack, then DNN has to make substantive changes to be able to run on the core .Net CLR.  So when we talk about DNN and ASP.Net 5, we are talking about the part of ASP.Net 5 that is truly new, not the part that is being carried along for backwards compatibility purposes.

Joe Brinkman
DNN Corp.
New Post
1/17/2015 3:12 PM
So the hundreds of DNN modules out there won't work and their developers need to rewrite them?
HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtDetails?Details?

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.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?