3 ms·

But is it getting the maintenance necessary to be future-proof? Is it getting the updates/features/documentation/care first or is there some new better-loved mo

by pas 5y ago

But is it getting the maintenance necessary to be future-proof? Is it getting the updates/features/documentation/care first or is there some new better-loved more recommended, hyped solution?

dgellow 5y ago
I don't think anyone knows, not even Microsoft!
electroly 5y ago
The answer for awhile was definitely no, but now it's yes. They have re-committed to both WinForms and WPF. I would suggest that, when it comes to Microsoft technology, you don't want the hyped solution. You want the boring stable solution. Following Windows trends is a path straight to development hell. If you wanted something new and exciting you'd be writing a web app in the first place.
- minimouse 5y ago
  What do you mean by "now"? Did something happen this month? WPF and WinForms haven't seen much at all for... a long time. This comment sums it up well: https://news.ycombinator.com/item?id=29424984 https://news.ycombinator.com/item?id=29424984
  - electroly 5y ago
    .NET 6 was released last month. This is the first release when you can reasonably use Windows Forms and WPF with .NET Core; they've spent a few years getting those frameworks to that point. I'm not sure that addresses what the other commenter is talking about, though. In this thread we were talking about "maintenance" and "future-proofing" but that commenter is talking about major new features; I'm not sure that we're talking about the same things.
WorldMaker 5y ago
With a lot of the "WinRT walls" torn down and WinUI controls available "out of the box" in WPF today (.NET 5+), WPF is almost a best of both worlds providing both the access to "better-loved more recommended" solutions and having a somewhat contiguous path back to a strong legacy of older code (modulo what you think of the .NET Framework 4.x to .NET 5+ hump; it's not quite a "just rebuild and it'll work", but it's also not as bad as some developers imagine it would be). At this point, right now if you are looking to build a Windows 11-targeted WinUI "green field" project the current green path (and almost the only currently supported path) is to start with a WPF application in .NET 6 and pull in WinUI controls.

by pas 5y ago

But is it getting the maintenance necessary to be future-proof? Is it getting the updates/features/documentation/care first or is there some new better-loved more recommended, hyped solution?

dgellow 5y ago

I don't think anyone knows, not even Microsoft!

electroly 5y ago

The answer for awhile was definitely no, but now it's yes. They have re-committed to both WinForms and WPF. I would suggest that, when it comes to Microsoft technology, you don't want the hyped solution. You want the boring stable solution. Following Windows trends is a path straight to development hell. If you wanted something new and exciting you'd be writing a web app in the first place.

minimouse 5y ago
What do you mean by "now"? Did something happen this month? WPF and WinForms haven't seen much at all for... a long time. This comment sums it up well: https://news.ycombinator.com/item?id=29424984 https://news.ycombinator.com/item?id=29424984
- electroly 5y ago
  .NET 6 was released last month. This is the first release when you can reasonably use Windows Forms and WPF with .NET Core; they've spent a few years getting those frameworks to that point. I'm not sure that addresses what the other commenter is talking about, though. In this thread we were talking about "maintenance" and "future-proofing" but that commenter is talking about major new features; I'm not sure that we're talking about the same things.

WorldMaker 5y ago

With a lot of the "WinRT walls" torn down and WinUI controls available "out of the box" in WPF today (.NET 5+), WPF is almost a best of both worlds providing both the access to "better-loved more recommended" solutions and having a somewhat contiguous path back to a strong legacy of older code (modulo what you think of the .NET Framework 4.x to .NET 5+ hump; it's not quite a "just rebuild and it'll work", but it's also not as bad as some developers imagine it would be). At this point, right now if you are looking to build a Windows 11-targeted WinUI "green field" project the current green path (and almost the only currently supported path) is to start with a WPF application in .NET 6 and pull in WinUI controls.