Posted By tony bonn on 9/1/2024 9:28 AM

Posted By Daniel Valadas on 8/31/2024 12:39 PM
> a major fortune 20 company who will not let me run .net framework for security reasons
So they don't use Windows, Excel, Word, SharePoint, IIS, Exchange?
Of everything I heard about people refusing .Net Framework for irrelevant reasons, security is the least justifiable.

> The only problem we have standing in our way is money, time and resource
No, the extensibility architecture of DNN is all webforms based, unless something extraordinary happens to make webforms work on .Net (core), we can't migrate no matter how much money and resources you throw at it. And that will make it so most 3rd party extensions would not work.

There are other .Net (core) CMS, they use shiny new stuff but don't have the maturity and ecosystem of DNN.

regarding security, firstly running the latest software is an owasp principle for guarding against and/or remediating security deficiencies. microsoft and all vendors, whether or not contradictory or hypocritical, fear monger with that idea. every time i start java, oracle blares the dangers of running software which is a few weeks out of date let alone a few years. in any event, at the end of the day, whether or not there is an objective security risk, corporate security has the last say, and in my case, and i am certain i am not alone, running .net framework is not allowed. i wouldn't even be allowed to run .net core 3.1 (although the issues there are admitedly different).

I want to be VERY clear just for those that are not as familiar with things.

.NET Framework - Is FULLY supported by Microsoft and DOES receive security updates and other items as needed.  Under OWASP guidelines and otherwise it would be more than acceptable to be continuing to use .NET Framework.   Yes, you need to be on 4.8 or 4.8.1, but that is easy and DNN and others are there.  (https://dotnet.microsoft....cy/dotnet-framework)

.NET Core - Your note about 3.1 is 100% correct, it is NOT supported and should NOT be in production.  There are a LOT of dates and differences between LTS & current, the full listing is here - https://learn.microsoft.c...oft-net-and-net-core

.NET Framework isn't the new & shiny, but we do have an entirely different security profile, given that .NET Framework is updated by the OS and managed through those patching processes.

Edited to add link about other .NET/.NET Core support dates

I agree with everyone. But I think Tony's point is that DNN needs to move to what Microsoft want. Developers want to use .Net Core and it will eventually go there, the question is when. And I personally think we have a long time before .Net Framework is a problem. My believe is that is the majority of our clients don't know and don't care what CMS they use. That is NOT true for all clients.

I looked at orchard, and I think it was good. But DNN is far better. The only problem with DNN is the "It's on old tech" comments. But the sad truth is, that is enough to make people not want to use it.

My favorite would be Oqtane CMS, but I do not believe Blazor is a good solution. If Blazor gets stripped out Oqtane I may reconsider.

Like I said before and many times to people, I decided to stay with DNN because it's the best tool and it is supported. I believe in DNN and the guys that maintain it so much that I have dedicated the last 3 years to rebuilding all our inhouse modules, which we have made many open source. https://www.rocket-cds.org/ (Not officially released, we're doing live tests)

Not everyone has that opinion.

This is an old topic and it's been going for over 5 years, I think people need to make their own mind of what is good for them.

What I miss in this discussion is the customer. When it comes to enterprise content management, DNN is still and by far my first choice. All functionality for editors and webmasters is very mature and if there is no UI, the system is open and extendable. I have had to work with worse. Much worse.

But DNN is challenging to recommend for new, larger customers. They make choices for the next 15 to 20 years.
Actually, being open source and MS-based is a great position for DNN. It allows government bodies and larger corps to be in their favorite architecture. And at the same time you don't need to change systems every 5 years because of tender regulations.

But looking ahead is the key issue from business perspective. At this point in time, the best answer I can give would be something like 'I can guarantee for the next 7 years'.

Those type of customers need more. If we don't have a plan to upgrade to .NET Core, we need at least a shared vision on where to migrate to. And how.
If we avoid this question, the only option for larger corps and government bodies that are looking for a platform for online communication, is Umbraco. Which is still by far not as good as DNN for editors, marketeers end webmasters.