3 ms·
Those are the true native style for Windows, yes. Microsoft's subsequent efforts aren't as good and they've not even fully committed to them themselves. WPF is
by pjc50 6y ago
Those are the true native style for Windows, yes. Microsoft's subsequent efforts aren't as good and they've not even fully committed to them themselves. WPF is on life support.
- 72deluxe 6y agoWOF is on life-support?? What do they recommend now then? I know in C# land WinForms was discouraged (no idea why) but what do they recommend now?? What is the "native" toolkit for modern C++ apps on Windows? I end up using wxWidgets because it is easy.
- pjmlp 6y agoFrom Microsoft offerings for C++ devs, just keep using MFC, or in your case wxWidgets. They will mention WinUI, but the team pushing for C++/WinRT killed all VS tooling support that C++/CX, so for doing WinUI with C++ you are stuck editing IDL files without any kind of VS tooling support, and also have to copy/merge the generated C++ files of the IDL ones.
- marsven_422 6y agoFor the love of God do not use MFC in 2021!
- pjc50 6y agoI 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.
- pjmlp 6y agoThat is what WinUI team would wish, but given that currently with version 3.0: - Only C# and C++/WinRT apps are supported - Desktop apps support .NET 5 and C# 9, and must be packaged in an MSIX app - No XAML Designer support - New C++/CX apps are not supported, however, your existing apps will continue to function (please move to C++/WinRT as soon as possible) - Unpackaged desktop deployment is not supported - When running a desktop app using F5, make sure that you are running the packaging project. Hitting F5 on the app project will run an unpackaged app, which WinUI 3 does not yet support. -- https://docs.microsoft.com/en-us/windows/apps/winui/winui3/ https://docs.microsoft.com/en-us/windows/apps/winui/winui3/ Most of long time UWP belivers just packed our stuff and are back in WPF/Win32 land.