Yeah it's great improvement to have it nicely typed, but keep it static, I don't want to be DI-ing everything, especially when I'm just throwing together a prototype.
I want easy to use, not dogmatic adherence to ideals that gain you absolutely nothing but a confusing mental model in something like semi-permanent config.
ODataControllers are some of the most painfully bad things I have ever had the displeasure of programming with, I'm migrating our code bade back over to using API controllers with the semi-broken OData plugins rather than use them.
Admittedly part of that is because OData is great for plugging into grids like datatables for jquery or kendo grid, but otherwise incredibly over-complicated.
It sometimes feels as if they can't make their mind up about anything, and yet invest heavily in the latest fad that disappears a year later.
Surprised they've not released an update yet that forces everyone to use yarn instead of nuget.
Web forms are from 2002. It‘s ancient by today’s standard, much older than e.g. facebook or youtube.
Apparently Xamarin.Forms alongside XAML Standard is going to be the UI story for .NET Core, as communicated at .NET Conf 2017 sessions.
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.
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.
Rewriting framework and standard libraries — I’m sure that will be nice after a while, but I’ll sit this transitional phase out.