3 ms·
I basically agree with pjmlp: Win32/MFC has always worked and will continue to work. > in C# land WinForms was discouraged Portability, it seems. Not unreason
by pjc50 6y ago
I basically agree with pjmlp: Win32/MFC has always worked and will continue to work.
> in C# land WinForms was discouraged
Portability, it seems. Not unreasonably, they're focusing on C# as a backend language in UNIX-like environments. While you can run WinForms from dotnet core, doing so adds a large chunk of libraries to your deployment and of course only works on Windows targets. I'm not sure I entirely approve of this direction, but it follows from targeting Java, and I do prefer C# to Java.
Of course, if you just want a little bit of the API, there's nothing stopping you from just p/invoking it out of user32.dll, which I did last month ...
- MaxBarraclough 6y ago> While you can run WinForms from dotnet core, doing so adds a large chunk of libraries to your deployment Sounds like the direction Java took, moving JavaFX (a rather underrated GUI toolkit from what I can tell) out of the core Java standard library.