WPF VS Roslyn

Gear up, folks, and test drive this fresh-off-the-lab feature. And should you stumble upon any glitches along the way, don’t hesitate to reach out. Got a bug to report or feedback to give? Send them directly to our dotnet/wpf repository. We’re eager to hear from you, because together, we’re only going to make the experience even better!

I did some research and did not find any proof of the EOL on WPF. In fact, Microsoft just updated the roadmap on WPF 2 months ago.

There’s still room for improvement though. I should add, WPF on .NET Core consumes a lot of memory, due to a memory leak. It was logged by our COO as one of our users was doing a comparison.

have you tried this?

WPF: Licencia MIT.

Some added context: It's a side effect of how variable rendering works in UI library we use. There's currently sadly no way how to disable VRR compatibility, which causes the issue you describe unless you tell your GPU to not treat Playnite as VRR compatible. Some more info here.

WPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.

This article only sights a video stream. I think part of the problem with the glacial pace of development is reliance on manual testing. See this comment:

https://github.com/dotnet/wpf/discussions/7130#discussioncom...

> Our primary goal is to ensure reduced turn-around-times for new PRs as well as clear the pending backlog of existing PRs. To that end, we are working on putting appropriate automation in place to reduce the dependency on manual testing as much as we can.

See also the recently updated WPF roadmap:

https://github.com/dotnet/wpf/blob/main/roadmap.md

If you look at the history of this file you can over the years tests have been always been in the backlog.

As for “where projects go to die”, they have 3 features planned for this year: Windows 11 Theming, a new type of folder browser, and null ability annotations. And they say they don’t think they can do them all. Maybe I’m underestimating, but that’s not a lot.

My understanding is that the .NET team is working toward this with Interceptors: https://github.com/dotnet/roslyn/blob/main/docs/features/int...

.NET is a little smarter about switch code generation these days: https://github.com/dotnet/roslyn/pull/66081

Recently, while creating some experimental C# source code generators (xafero/csharp-generators), I was just concatenating strings together. Like you do, you know, if things have to go very quickly. If you have a simple use case, use a formatted multi-line string or some template library like scriban. But I searched for a way to generate more and more complicated logic easily - like for example, adding raw SQL handler methods to my pre-generated DBSet-like classes for my ADO.NET experiment. You could now say: Use Roslyn and that's really fine if you look everything up in a website like SharpLab, which shows immediately the syntax tree of our C# code.

At runtime, the Case C# expressions are embedded into a function and dynamically compiled into an assembly using the Roslyn C# compiler. Then the function that contains the expression is called (e.g. CaseAvailableFunction.Availablle()). At runtime, the function provides various methods to access stored case values as well as the current input data.