4 ms·
what Microsoft fat client technology are you using? the current problem for me with Microsoft fat client is there are too much options and no clear one that Mi
by MangoCoffee 5y ago
what Microsoft fat client technology are you using?
the current problem for me with Microsoft fat client is there are too much options and no clear one that Microsoft will support long term.
- ryandrake 5y agoYea, I develop a hobby project targeting desktop Mac (Objective C GUI, C++ business logic) and I’m not sure what Windows technology I should use should I ever decide to port to Windows. There are so many and they are all in various stages of unsupported. C#? C++? .NET? Win32? MFC? WPF? XAML? WinForms? UWP? Maybe just give up on trying to read the future and use Qt. Fucking madness!
- kaetemi 5y agoC# 2.0 WinForms, or Win32, for simple run-anywhere tools with no dependencies. Qt 5+ for anything with any level of complexity. Windows has already given up on 'native' UI. JUCE for audio plugins. Don't bother with all the 'modern' pretend-windows-is-a-touchscreen-os frameworks.
- jfk13 5y agoI faced that question over a decade ago, and after looking around at my options, I went with Qt. No regrets. Sure, it had its flaws, and sometimes the "not-quite-nativeness" shows through, but it worked pretty well and gave me support for all 3 major desktop systems. And although someone else has long since taken over maintenance of the application in question, it's still going strong (and still built with Qt).
- ripley12 5y agoIt's a mess. If pressed I would say WinForms is the most practical choice for most apps today - even though it sucks, even though it's ugly. It's actively worked on (unlike WPF) and it lets you use the latest .NET version. WebView2 (better Electron) is probably where most Windows development is going in the future, the Windows team is investing a heck of a lot more in it than other technologies.
- tasogare 5y agoC# on .net 6.0 with either WinForms or WPF.
- foepys 5y agoDo not use WPF. WPF is dead. If you don't want to use WinUI, go with WinForms.
- vborovikov 5y agoWPF isn't dead, it's done.
- tonyedgecombe 5y agoIt's never looked finished to me, it was abandoned at birth.
- pjmlp 5y agoBeside all the sibling comments, avoid WinUI, regardless of 2.x or 3.x variants. They deprecated .NET Native and C++/CX and are yet to provide any tooling that compares to them. .NET Native is stuck in C# 7, while C++/CX got replaced by C++/WinRT with the argument that it is ISO C++ friendly, when in reality it offers the same tooling as using Visual C++ 6.0 with ATL back in the days before .NET came to be, but their developers are so stuck in COM pre-historic tooling that they don't acknowledge that. Apparently WinUI 3.0 would be the future, with the merge WinRT and Win32, however issues pile up exponentially and even Windows 11 is making use of the deprecated UWP, as the team cannot keep up. Since MAUI depends on WinUI 3.0, it is yet another reason why it keeps being postponed. Windows on 2022 with Microsoft stacks MFC (yes really, much better than C++/WinRT), WinForms or WPF (eventually with C++ if required). Otherwise Qt, Delphi or C++ Builder if enough budget, or PWAs if possible to do so.
- moonchrome 5y agoWe're talking Microsoft here, they will probably be patching any crap they put out 10 years from now to maintain some enterprise app nobody knows how to update. Even when they gave up on Silverlight it was supported for almost 10 years afterwards.
- fxtentacle 5y agoDirectx for everything to make things fast and to get nvenc hardware encoding. Imgui and juce are great frameworks.