Re:Book of the Runtime – Internals of the .Net Runtime not i...
by megaman22 on Thursday September 28, 2017 @08:04PM
(#15361786)
WinForms will never die.
Re:Book of the Runtime – Internals of the .Net Runtime not i...
by pjmlp on Friday September 29, 2017 @02:08AM
(#15363114)
There are people still writing fresh COBOL and RPG code in 2017 as well.
I do have an ongoing WinForms project, but only because it integrates with an application that was initially developed for Windows XP.
XAML designers, specially Blend, are much more powerful than the WinForms one.
Re:Book of the Runtime – Internals of the .Net Runtime not i...
by cm2187 on Friday September 29, 2017 @02:50AM
(#15363300)
But the reality is that when I want to create a simple UI to automate a task or visualize something internally, winform is just perfect. None of my users care whether there is a flashy colorful touch friendly UI or a bunch of grey forms. They are all going to run it on crappy workstations running windows 7 anyway. And it's not about the UI, it's about the numbers that it shows.
Re:Book of the Runtime – Internals of the .Net Runtime not i...
by pjmlp on Friday September 29, 2017 @03:58AM
(#15363524)
XAML designers can be used just like Forms for those purposes.
Dropping elements from the toolbox into the form, setting properties and code-behind event handlers.
No difference here, there is no need for MVVM over-engineering if the requirements are basic as you say.
With the advantage that XAML layouts are much easier to work with than TableLayoutPanel.
Apparently Xamarin.Forms alongside XAML Standard is going to be the UI story for .NET Core, as communicated at .NET Conf 2017 sessions.