4 ms·
You can do the "WinForms approach" with WPF/XAML still, but once you got the ideas and concepts behind MVVN, observables, bindings, converters, collection contr
by numlock86 6y ago
You can do the "WinForms approach" with WPF/XAML still, but once you got the ideas and concepts behind MVVN, observables, bindings, converters, collection controls and so on, there is absolutely no turning back and you start to miss that stuff on WinForms.
- privateSFacct 6y agoIs WPF/XAML the right way now to do quick get going windows app development?
- tonyedgecombe 6y agoIt wasn't for me, it felt like wading through treacle. However if you want to unit test your UI then it makes more sense.
- ChicagoDave 6y agoStill think WPF/XAML was the best layout engine and I'd cry if it replaced CSS.
- pjmlp 6y agoYes, although the future is WinUI. https://microsoft.github.io/microsoft-ui-xaml/about.html https://microsoft.github.io/microsoft-ui-xaml/about.html
- pjmlp 6y agoYou can partially use them on WinForms, I have done so in several projects. https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.bindingcontext?view=netframework-4.8 https://docs.microsoft.com/en-us/dotnet/api/system.windows.f... It isn't as powerful as WPF/UWP, and it has some caveats depending on the .NET Framework version, but it does the job.