dotnet VS ProjectReunion

Microsoft .NET Blog: https://devblogs.microsoft.com/dotnet/

Just find some good sites, that keep up with the news/changelogs ( one that I like for c# / dotnet stuff is is: https://devblogs.microsoft.com/dotnet/) as well as the whole c# roadmap on github and where they propose features, and design meetings (https://github.com/dotnet/csharplang/tree/main/meetings). It provides a lot of insight on what they plan on doing with the language). That's usually where I go to keep up with c# stuff.

Microsoft's .NET blog is pretty good for seeing what they're up to.

The .NET Blog has great articles about new and upcoming changes.

how exactly does dotnet 5 acheive this? it makes sense for dotnet 6 since we have different TFM's like net6.0-android, net6.0-ios, net6.0-macos etc. however, if you look for dotnet 5 you only have net5.0 and net5.0-windows TFMs as per given link, https://learn.microsoft.com/en-us/dotnet/standard/frameworks also somebody asked the question how to run .net 5 app on android and the answer given was to preferably still use xamarin/mono, https://github.com/microsoft/dotnet/issues/1253 Also what exactly did change in this regard, does it use same core clr, does it use the same base class library as one used in dotnet core?

Bookmark https://devblogs.microsoft.com/dotnet/ and read occasionally. https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csh... is good for a quick overview of language features depending on what version you're at.

Most .NET devs only need to be peripherally aware of these changes, as most businesses using .NET will move slower than Core's new pacing. It's even less important for lower seniority devs as you typically need project changes to utilize new features, which is a call a senior would make, which involves approval/testing/deployment, so a slow process which gives you time to read up on the new features as they're needed.

You're better at your "craft" the more tools you know about and how to apply them, but if your day job prevents you from following the new stuff, I wouldn't worry too much about it.

>I feel .NET Core after a good start is falling into the typical Microsoft trap of constantly cranking out new stuff to do the same thing and leaving it to developers to keep up.

Yeah, the pacing has increasing dramatically from .NET Framework days, but that's probably a good thing. I would just stick to learning about what you do in your day job. .NET has a huge ecosystem compared to other languages, so it's going to be very hard to keep up with everything MAUI is doing if you're doing regular ASP.NET core APIs.

Release Notes

.NET home repo - links to hundreds of .NET projects, from Microsoft and the community.

The issue is described here: WebView2 does not support passing in a CoreWebView2Environment · Issue #1170 · microsoft/WindowsAppSDK (github.com)

.. and how many of the Microsoft applications actually use WinUI3? As far as I can tell they're doing their own thing (Office) or are Electron (Teams) or, at least in Windows 10, haven't actually been updated from WinForms.

The overhead of WinUI3 is pretty huge. The visual designer, a winning feature of Visual Studio for decades, is AWOL. Why? It's XAML, the same as the previous XAML designer! It's just .. broken?

The backward compatibility story is a disaster: you can get stuck in the UWP sandbox https://github.com/microsoft/WindowsAppSDK/issues/1780

What's the big Microsoft WinUI3 flagship app, then? Something people are actually using? Rather than just a few system dialogues. (How many Win11 settings pop up a Win32 dialogue box, still?)

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

As far as I know, there are still some issues with OIDC integration. See this, for example.

this I'm interested in. WinAppSDK is open source.

I think the issue is actually the sandboxing and other stuff. WinRT StorageProvider API is known to be extremely slow and NTFS / Windows IO subsystem is itself already quite slow compared to UNIX. The issue IIRC is that StorageProvider is designed for sandboxing and the way they implemented that involves doing RPCs to other processes. So there's probably some heavy context switching involved, but it's architectural, and so the voice recorder was never fixed.

https://github.com/microsoft/WindowsAppSDK/issues/8

Disclaimer: I work for Microsoft. I even work on WindowsAppSDK just not the WinUI parts. People far more graphically inclined and talented than I handle that 😀