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

HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtRelease date?  Work Started?Release date? Work Started?
Previous
 
Next
New Post
2/19/2016 2:11 PM
 

We, DNN Corp, will not be releasing a vNext based product in 2016. Although not set in stone, it is highly unlikely we will even start development on a vNext based version in 2016. 


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
2/20/2016 6:05 AM
 
Tony Henrich wrote:
Sebastian Leupold wrote:
AFAIK there had been first investigations last year (mainly by Charles Nurse).

That work is about MVC modules and it's old stuff. 8.x already supports MVC modules (well some of MVC). vNext is pure MVC and no WebForms.

No, I know for sure he did some initial tests, but that took place before he had to leave DNN Corp.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/28/2016 8:53 PM
 
Chris Paterra wrote:

We, DNN Corp, will not be releasing a vNext based product in 2016. Although not set in stone, it is highly unlikely we will even start development on a vNext based version in 2016. 

These are very bad news since that means no shift to the essential new features ASP.NET 5.0 can provide. I knew that the old roadmap was too positive in thinking but this means no ASP.NET 5 until 2018 or later: two years (!) from now on. Very sad to hear that, I hope DNN will not stay behind.

 
New Post
6/4/2016 10:07 PM
 
Personally, I believe that DNN should not drop support for current technologies until Microsoft themselves does. After all, that will kill all of the current modules we have right now. wwhy, after all, then, does microsoft have two aSP.net frameworks? Use new technologies where they are needed, not just because they're all the rage. I'm happy that the official consensus is to wait. In this way, everyone gets a chance to catch up, test rewrites of their modules, and what not.
 
New Post
6/7/2016 1:40 PM
 
This is certainly an area where I think being conservative is wise. DNN isn't the new hot CMS... it's an established platform currently being used in a great variety of industries and deployments. I'd rather it move slowly on major transitions.
 
Previous
 
Next
HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtRelease date?  Work Started?Release date? Work Started?


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