Hello Guys, we've recently discussed the upcoming .NET 5 migration with Martin Praxmarer (aka Noxe), a DevExpress MVP, in person and continued in public now: https://supportcenter.devexpress.com/ticket/details/t923208/model-editor-cannot-open-the-net-core-editor-version-for-a-standalone-net-standard
I think you will be interested in this discussion too:
Some months ago Microsoft announced upcoming changes in https://github.com/dotnet/designs/blob/master/accepted/2020/net5/net5.md. Yesterday, they finally announced its implementation in https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-8/. As I understand, .NET Standard becomes outdated too with the .NET 5 release:
net5.0. This TFM is for code that runs everywhere. It combines and replaces the netcoreapp and netstandard names. This TFM will generally only include technologies that work cross-platform (modulo pragmatic concessions, like we already did in .NET Standard).
My current thoughts for XAF (Blazor, WinForms and EF Core) is that we should abandon .NET Standard 2.0 and .NET Core 3.1 assemblies for this new development and ship only .NET 5 in v20.2. Even though .NET Core 3.1 is LTS until December 2022, I think it is not needed much by customers due to the CTP state of XAF features that are based on this target platform. Of course, .NET Framework assemblies will be shipped as before or will be unaffected. What do you think?
Please share your thoughts on this, if you have a minute or two.
@biohazard999 , I will definitely think about it more and make a presentation when this community standap gets 100 online XAF customers :-)
In the meantime, we will keep teasing the latest XAF development news in this chat, SM, our team blog and, of course, the community standup when I participate in it.
BTW, what topics do you want to get covered most?
We did and will do our best to address the needs of existing ASP.NET Web Forms UI users. For instance, we fix bugs every week (2 devs from the Blazor squad do ASP.NET Web Forms maintenance half of their time).
Thanks for the reply @dengara_gitlab and the frequent communication here. I'm excited to dive in and start testing my app with the Blazor front-end. It's clearly maturing quickly.