Remove .Net Standard

[Mimetis]

It's becoming harder to maintain a .NET Standard version.

Are you still using .NET Standard ?
Is it ok to remove .NET Standard supports and supports only .NET versions > .NET 6.0 ?

[VagueGit]

UWP devs are stuck on .NET Standard. .NET 9 support for UWP is currently in preview

Maybe support .NET Standard for 12 months after .NET 9 support for UWP is released? This gives UWP devs time to upgrade.

[Mimetis]

oh nice, didn't see that .NET 9 is going to support UWP !

[VagueGit]

The idea is to make it easier for devs to migrate from UWP to Win UI and MAUI, so presumably there will be at time when UWP goes out of support. So we'll be looking for DMS support for Win UI and MAUI please as those tools become available.

[NancyFolsom]

I am stuck with standard for the foreseeable future. Especially since my client is a U.S. government agency and who knows how funding will be available for a redesign that drops the framework I'm tied to.

[JScrivo]

I am stuck on framework 4.7.2 for my client app foreseeably for the next 2-3 years so it could create compatibility issues for me. :(

[NancyFolsom]

Me, too. As much as I'd like to move them off 4.7, they have to find budget for it. I've been working on them for a few years now to plan and work on an upgrade, but it'll be a complete rewrite which is hard for customers to stomach. Esp. hard at the moment in the U.S.

Edited to add: I mentioned DMS likely dropping support for classic .NET for necessity, which is 100% reasonable, IMO. That might help.

[Mimetis]

@NancyFolsom If it can help your customer move forward, that's a good reason :D

[NancyFolsom]

They're not opposed to upgrading just because they don't want to deal with it. If there's no budget to rewrite the entire application, then there is simply not the budget, and it would take time.