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 neXtMigration Plan & Development RecommendationsMigration Plan & Development Recommendations
Previous
 
Next
New Post
1/25/2015 6:25 PM
 

As we embark on this journey to support the new technology that is out here.  Regardless of the thoughts that anyone might have regarding proper fitment etc.  I think a healthy discussion around the migration plan and development recommendations needs to be an early thought in this discussion.  A few key points and areas of consideration lead me to this.  This is based on my own questions as well as those of my customers in the past months.

  1. At the current time the future is a bit cloudy.  New sites are being built, some with literally months and months of effort with multiple team members to build.  If they select DNN as a new platform, or even if they are currently on it but continuing to prosper what is the future like for all of this work.  How soon can a migration plan, or even a "quick tips" recommendation be created to ensure that they will have as seamless of a transition as possible.  
  2. Along with the above for new development.  WHat about those with older modules.  Many of us have code that might have been written in the mid-2000's and it still works.  Is there any effort that we should take today to help bring these elements forward?  
  3. Should the long overdue discussion of removing Deprecated methods actually be done to help make things easier.  Some of the recent 7.x re-structuring of API's has made the environment VERY hard for new users to come into the environment.

I have a few ideas around this.  For example for #2 above, I have been recommending to people that they compile against the latest release and resolve any Deprecated method calls at a minimum.  

Just a few thoughts on the "migration" that will be part of this.  


-Mitchel Sellers
Microsoft C# MVP, MCITP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
1/25/2015 6:40 PM
 

some quick responses:

1. this is difficult to say as we are only in the early stages of neXt, some of the decisions that get made in the next months will determine the approach to migrating. There are many options e.g. supporting portal templates, providing data import utilities etc. Suffice to say we will be working hard to make any migration as easy as possible, and to preserve as much functionality as possible.

2. this is a little easier to say - we've previously announced that in 7.5.0 we will be making efforts to mark any methods/classes that are not going to be brought forward as obsolete. This means that developers can compile against 7.5.0 and see if they're code (or at least the non-presentation aspects) will be transferable. In addition we will be introducing MVC and Single page application (SPA) module extension types - these will align as closely as we can get with .net 5.0 (there are likely to be a few breaking changes), this means dev's can transition webforms based modules to either of these approaches and then hopefully move them across to neXt with less development effort

3. We are obsoleting any additional classes/methods in 7.5.0 that will not be brought over i.e. they will be obsolete in 7.5.0 but will not exist in neXt


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/25/2015 6:45 PM
 
BTW it's easy to follow along with any changes by watching jira or by looking into github e.g. https://github.com/dnnsoftware/Dnn.Pl... shows that work is underway to extract all the admin/host modules to their own installable modules, as well as adding support for MVC .

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/27/2015 1:25 AM
 
Thanks Cathal! This will help me get ready for my new blog series that I'm thinking of starting.

-Mitchel Sellers
Microsoft C# MVP, MCITP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
1/27/2015 8:38 AM
 

Realistically, DNN 7.x still has at least 3-4 more useful years for the platform. Even once DNN neXt comes out there will be plenty of time for customers and consultants to figure out how to transition to the new platform.  People should not get too excited today about what the migration path looks like just yet, but as Cathal points out, there are some things you can do today which will help minimize the amount of migration effort needed in the future.  As we get closer to Summer, things will come more into focus with DNN neXt as we will have some working code so people can get a better feel for the next generation.  

Also, beyond just thinking about what the migration path looks like, it would be a good time to start educating yourself on ASP.Net 5 and possibly Entity Framework 7.  There is a bit of a learning curve involved if your primary experience this past decade has been Web Forms and DAL.  While nothing is completely set in stone, we know that the current DAL will not run on the Core CLR.  We rely on an ancient part of the Enterprise Library (Data Access Block) and PetaPoco, both of which are not compatible.  As a result we are re-looking at our Data Access options and my use this opportunity to use something a little more modern as our base data access technology.


Joe Brinkman
DNN Corp.
 
Previous
 
Next
HomeHomeFuture Developm...Future Developm...DNN neXtDNN neXtMigration Plan & Development RecommendationsMigration Plan & Development Recommendations


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out