Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


You can partially use them on WinForms, I have done so in several projects.

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.


Is WPF/XAML the right way now to do quick get going windows app development?



It wasn't for me, it felt like wading through treacle.

However if you want to unit test your UI then it makes more sense.


Still think WPF/XAML was the best layout engine and I'd cry if it replaced CSS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: