3 ms·
They just keep recognizing that WinForms is the best. And you can still use it
by yread 5y ago
They just keep recognizing that WinForms is the best. And you can still use it
- cm2187 5y agoDo they have full support in .net 6? I believe in previous version it was a partial/beta implementation. Hardly any mention of winform in the announcement. I am basically stuck on .net 4.8 because of that.
- mastax 5y agoI just ported a WPF app where the story is similar. Yes, I'd call it "full support". It's not a drop-in replacement, though, except for really simple apps. Check the Breaking Changes List for .NET 6[0], .NET 5, and .NET Core 3.1. Some more niche APIs like `System.Runtime.InteropServices.RegistrationServices` are not supported on .NET 5+ at all. If you have NuGet packages that haven't been updated since 2011 you may need to find modern replacements. There is an Upgrade Assistant tool[1] which can do much of the work. You'll probably have to spend a few annoying hours googling and editing .csproj files by hand. [0]: https://docs.microsoft.com/en-us/dotnet/core/compatibility/6.0#windows-forms https://docs.microsoft.com/en-us/dotnet/core/compatibility/6... [1]: https://docs.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-winforms-framework https://docs.microsoft.com/en-us/dotnet/core/porting/upgrade...
- ripley12 5y agoWinForms support in .NET 5 and 6 is great. It's getting a lot more attention than WPF (which is owned by the Windows team), and it's likely that in .NET 7 it will be trimmable and maybe even AOT-compatible.