Hacker News Reader

Comment by privateSFacct | Hacker News Reader

Very helpful. I thought WPF / Core was the recommended / modern approach.

I just fired up an attempt using Windows Forms / Net Framework after scrolling down to that combo. It looks good so far.

View on HN

Yeah, I think the Microsoft messaging would naturally lead you to that conclusion, though generally they avoid saying it explicitly. I think in a year WPF and WinForms will probably work great under .NET Core, but I wouldn't use either for real work right now. My recommendation would be to use .NET Framework for GUI work right now, but do it in such a way that the upgrade path is easy. The way to do that is to create the project under .NET Core, and then hand edit the project file to change the <TargetFramework> element from "netcoreapp3.0" to "net472". That will give you the new project file format and make it easy to upgrade when they finish getting the bugs out. The other main thing you should do is to create any libraries as .NET Standard 2.0 libraries, which work with both .NET Framework and .NET Core.

Can you put WPF code in .NET Standard 2.0 libraries somehow?

> I thought WPF / Core was the recommended / modern approach.

The recommended / modern approach for 100% new applications would probably still be UWP (WinRT XAML) / Core, except getting that up-to-date with the latest .NET Core improvements is currently delayed until .NET 5.

Await the November update. When I remember right, they will update the designer till then.

Reply on news.ycombinator.com