Re:C# 9 top-level programs and target-typed expressions
by Semaphor on Tuesday March 30, 2021 @10:37PM
(#26642944)
> There are many paths out of hell.
Unless you are maintaining a Webforms project :(
Everything new is core or now .NET5, but I see no way to migrate our main website without essentially stopping all other development work for a long time.
Re:C# 9 top-level programs and target-typed expressions
by thrower123 on Tuesday March 30, 2021 @06:16PM
(#26641260)
I'm pretty sure WinForms is being migrated. I've built dotnet 5 WinForms apps, anyway. At least on Windows - I wouldn't bet on a Linux Gtk/Qt port any time soon.
WPF is probably dead though.
Re:C# 9 top-level programs and target-typed expressions
by tekdude on Tuesday March 30, 2021 @08:47PM
(#26642316)
WPF is quite alive. I had a pretty big audio processing project using WPF a while back, and when I migrated the codebase from .NET Framework to .NET Core 3.1 (and now .NET 5), there were surprisingly noticeable responsiveness improvements. I think they also have some more improvements planned for .NET 6 as well.
Self plug: A while back, I split off my own WPF MVVM framework from that larger project. It's designed for building simple touch-style interfaces, like you would see on a phone/tablet: https://tinyurl.com/upbeatui
Re:C# 9 top-level programs and target-typed expressions
by ziml77 on Tuesday March 30, 2021 @08:27PM
(#26642179)
Microsoft wouldn't let WPF die. Anyone writing enterprise desktop applications is using it heavily.
Re:C# 9 top-level programs and target-typed expressions
by tonyedgecombe on Wednesday March 31, 2021 @01:33AM
(#26643855)
Anyone writing enterprise desktop applications is using it heavily.
I don't think there is much of that going on anymore.
In reality Microsoft did let WPF languish for years, it always felt unfinished. I was very surprised when they migrated it to .Net core.
https://docs.microsoft.com/en-us/dotnet/core/porting/windows...
Winforms is probably a no-go on migration, but you should definitely check out Blazor if you want to develop any new business apps. We have constructed some incredibly complex business dashboards using this framework and cant imagine how some of this would even be possible if we had to move back to a front-end client framework and invent a bunch of JSON APIs.
Also, the new Blazor Desktop stuff is extremely exciting:
https://medium.com/young-coder/blazor-desktop-the-electron-f...
> The first difference is that the WebWindow container doesn’t use WebAssembly at all. Yes, you can run more or less the same Blazor application in WebWindow as you would in a web page. But when you use a web page, it’s executed by a lightweight .NET runtime that’s powered by WebAssembly. When you use it in WebWindow, it will use the cross-platform .NET runtime directly.
There is a lot of really amazing stuff coming down the roadmap, so I can easily advocate for enduring some degree of pain to get on this wagon.