At this point in time, the plan for .NET Core support is most likely going to have to Shift in nature to that of going directly to 3.x due to the support policy of .NET Core.

Right now, Blazor is NOT on the target for support at this time with the transition. However, we do not have a solid timeline on any transition to .NET Core yet either.

I am going to start directing my efforts towards version 10 and I am looking at Andrews recommendations for next steps. I am going to create a thread here to discuss each one I believe. We need to accelerate this project to meet community goals and I need some help to help :)

I think Blazor is going to be a cool feature for module developers. I was hoping to hear we are going straight to version 3 so that is good news to me and makes total sense.

I know a lot of this is new to most of us. I want to be full stack .NET Core DNN Version 11 developer and wish to dig deeper here soon into the core of the DNN Platform. I would love to see a much cleaner application code without all the obsolete and future deprecated code clogging up my mind ASAP so I can get to work on features instead of migration work :) Only so many hours in the day so doing what I can over the next year is my goal to see this get to version 11 alpha or beta release. If we can get one or two more talented software engineers looking to help a community like ours to join the fun we could meet that goal sooner. .NET Core I literally can almost taste it in my mind.

I don't want to stifle the enthusiasm here, but we WILL NOT be .NET Core for version 11.

My best conservative estimate is we need between 4,000 and 6,000 developer hours to get things moved to a proper .NET Core implementation. And that implementation will break things for > 60% of the modules in the marketplace so we will have to continue to be conservative in the plan.

We are 100% for going forward, but the community has voiced a STRONG desire for a migration pathway.

Way to burst my bubble :) I thought version 11 would surely be a .NET core version.

I guess I need to relook at this project then in a different way.

I think Micrsoft should kick down some developers here help us out!

I will start some noise that direction :)

I STRONGLY believe we need a clear and updated migration path plan.  Something that leaves out these kind of questions if it is going to take that long...  Andrew has a .NET core version going that is skeletons compared to what DNN has.

Half million bucks should cover it sounds like if you pay for it and there is a lot of contributions along the way from the community.  Is there anyone can put together a donation campaign to higher a company that is from the outside of the normal community that specializes in assisting with these types of projects?  Sure would be nice to see Micrsoft toss in a helper to guide the community further and get this done faster.  I am hoping to see someone step up out of no where and throw down some contributions since we cannot accept money. 

And for this it would be nice to keep a clear understanding for others who may be interested in helping a clear way to help with the .NET Core migration project.  I found the build feature in VS so look out maybe I can actually get something done here to help but I am no one compared to those that have done this before.  I just want to get down to learning and using one fairly straight forward stack that is modern and I can keep up wtih the changes a little.

It would be great to see the path and the next things that need developed to move forward instead of the entire process, however have that as well. And a guestimate of how many versions it will take to migrate everyone safely to the .NET Core version.

A page should be dedicated to this effort so anyone that wants to join in on the fun can help take a few hours off that timeline and excel development efforts.

I am studying quantum code now with MIT site info and other sources but I might just stay with .NET Core migrations.  I found some stuff related to it so I can really research a way to help the community move forward over the next year.  I am getting used to the work flow and setting up a way to be more productive coding...

I understand there needs to be a way for "legacy" modules to work and a way to create or migrate to "modern" .NET Core modules. Both worlds at the same time in DNN.

With everything catered to module developers there has to be some give and take here with the community.  I really want .NET Core sooner than later. Everything in the .NET world is around it.  I don't want to develop modules until we are there really but I will make a few to practice the migrations with.   I want to start using WEB API as well with REST services. 

So over the next year I should be able to enhance my skillset and throw down a little help when I feel I can.  I know it is a lot of thought and things for different reasons happening.

I just want to use the .NET CORE BLAZOR!!!! and I like DNN along with all yall community people :) I am highly motivated as when I want something bad enough it motivates me big time XD

Class is in session :)

Cody, I agree it would be nice to have a clear picture of the path to .NET Core, etc.  However, at this time, there are very limited resources and too many unknowns to start setting those sorts of expectations.  ;-)

You speak of migration of "modules" here, but it is unfortunately not quite that simple.  DNN Platform is built on :"ASP.NET Framework".  That is a different framework than "ASP.NET Core".  The entire foundation of DNN has to be rewritten in order to make a full transition to .NET Core.  One step that is being discussed, for example, is to make many APIs .NET Standard compliant (which can run on both "ASP.NET Framework" and "ASP.NET Core" - see https://docs.microsoft.co...et-standard for a nifty little chart on what versions of what work on what versions of what).  This effort alone could be 1000s of hours of effort.  Now, if we had a team of architect level engineers, this would be less of a mountainous task.  However, we don't.  We have a handful of people that are contributing to DNN Platform today and only a few people with the actual skill set to accomplish a feat such as this.  And, oh by the way, did I mention this is a 100% volunteer effort in an open-source project?  Hehe - hopefully, some of these statements are starting to make more sense now.

So, that said, the enthusiasm and passion is absolutely FANTASTIC!  We just need to temper our expectations according to the realities of the resources at play here - people, skillset, tools and time.  Let's be strategic moving forward.  Let's focus on the things we can make better and march forward with a setup for success!

I am working on a blog post to try and update everyone with regards to .NET Core and what it means for a transition for the DNN Community & Eco-System if we decide to continue down that route. Including the amount of development resources that we just do not currently have.

The complicated part with all of this is that there is no longer any way for the existing DNN & .NET Core to co-exist at the same time. The initially targeted "gentle" transition plan is no longer possible given the support lifecycle of .NET Core and feature sets included in the remaining supported versions of .NET Core. This means that a .NET Core break would render 100% of the Themes and 80-95% (estimated) of third-party and custom extensions as incompatible with a .NET Core version. Based on community feedback that sort of a all-in clean break is not desired nor supported.

Additionally, as much as I want to get new technology in, we have a lot of technical debt that needs to be cleaned up, regardless of the pathway forward and that is currently consuming almost ALL of the contributions by the community.

If we had a team of developers, all senior level, and a budget, we might be able to attack it, However, we don't have that level of engagement yet.

"You speak of migration of "modules" here, but it is unfortunately not quite that simple. "

I agree, this should be a real discussion so we all can understand.  I feel modules should be held up by module developers to keep up with the times. 

I believe if we can make DNN .NET Framework and DNN .NET Core co-exist so you can run both types of modules would be ideal here.  We already have half it done just need to really port a .NET Core app that clones the .NET Framework version.

Great talking points, I like the article you pointed out I will read it over and see if I can help.  If it is only 4000 hours I work about 8000 for a year we should have it half way there at least maybe :)

Thanks David.

If we had a team of developers, all senior level, and a budget, we might be able to attack it, However, we don't have that level of engagement yet.

 

I agree here as well. I think we need a kickstarter campaign here. I did calculations it should cost about 500K or so maybe less as community will be helping. Anyone hired out should be working with the community as well giving us feedback and helping manage the project during the transition is what I think we should consider. Set a goal to raise funds and ask donors for things like gold sponsorships or whatever to help make this a .NET Core friendly application.

Set a goal for 200K and who knows a silent donor might kick something more down to help it get there even faster and maybe set goals that if reached more things can get planned for development enhancing features for DNN. It just needs to be presented in a way that make sense and they feel they are a help. Maybe a donor can get a special donator badges to people that donate and we can move some gamification into DNN core. and .NET Core sponsors get a special recognition page for helping contribute funds to help get resources desired.  Gold Silver Bronze and Community Donor Badges!?

Other than that we are up a creek without a paddle right now for a long time it feels. I will step up to the plate more I think by this time next year I should be pretty versed in what is going on to help move things to .NET Core.

I read that it is fairly simple process however so many moving parts in DNN.

I will study more on this topic as the other i just dont think would ever happen and i want it to happen :) but I know it is massive undertaking keeping everyone content with changes that might be necessary.

But you can't make an omelet without breaking some eggs... Module developers that are active in DNN should be active in DNN contributions as well as I know a few of you are helping but we can use more efforts from anyone capable at this point.