It has been 2 years since .NET Core 3.0 added support for WPF, so it's time to drop support for the .NET Framework and focus on .NET.
There is a few reasons for doing this:
Build simplicity: multi-targeting .NET and .NET Framework adds some complexity to both the project structure and the build jobs, Builds usually take longer too, as they have to run the same tests in both frameworks. Shorter / simpler processes make me more inclined to work on the tool
User simplicity: I can imagine some users might get confused about which of the tool variants they need to download as well
Reliability: I don't always switch back and forth between target frameworks when working locally. This means I might miss some incorrect behaviour in one target framework which works perfectly well in the other
It's the future: by focusing on .NET, I can make use of some of the new C# features which were impossible to be used when multi-targeting. It might also simplify the migration of the tool to a different UI framework in the future (e.g. MAUI)
If you have any questions about this, feel free to post them here, even if the issue is closed (which will be pretty soon). Obviously, you will always have the choice of using an earlier .NET Framework release and not upgrading to a .NET one.
It has been 2 years since .NET Core 3.0 added support for WPF, so it's time to drop support for the .NET Framework and focus on .NET.
There is a few reasons for doing this:
If you have any questions about this, feel free to post them here, even if the issue is closed (which will be pretty soon). Obviously, you will always have the choice of using an earlier .NET Framework release and not upgrading to a .NET one.