search

SkyeHoefling / Dnn.vNext

MIT License
11 stars 7 forks source link

Support .NET Core 2.1 Minimum #25

Open mitchelsellers opened 6 years ago

mitchelsellers commented 6 years ago

Due to new features, and expected timelines ensure that .NET Core 2.1, or later, is used for the project

thabaum commented 4 years ago

Now that .NET Core version 3.0 is available can this be bumped up there or does it need to work with version 2 first? Reading this blog it discusses .NET 5 = .NET Core vNext with .NET Core 3.0 being able to do it all. 3.1 is in preview 3.

https://devblogs.microsoft.com/dotnet/introducing-net-5/

I also read the great info in your blogs posted in the DNN community discussion forums discussing the move for DNN. I am very interested in how this part will be working as I believe .NET Core spits out new versions continuously. Maybe I should move this discussion to the forum? Thank you!

mitchelsellers commented 4 years ago

For this we must stay < 3.0.

3.0 and later is not compatible with .net framework.

thabaum commented 4 years ago

OK so this looks like 2.2.8 is current version and 2.2.7 has security patch as shown here: https://dotnet.microsoft.com/download/dotnet-core/2.2 so this would make sense for what to expect?

Would that be more the correct version that DNN will potentially be running? SDK 2.2.207 version and the 2.2.8 Runtime needed to run the core app for the target? I look forward to playing with it when I have more time.

mitchelsellers commented 4 years ago

@thabaum Actually its a bit loaded question 2.2 actually is End of Life effective December 26th, 2019. (Yes, 1 month from today)

Our long-term plan is going to be a bit more complicated due to some of these changes in support policies etc.