ambie VS dotnet

Fortunately, System.CommandLine (in its current version, 2.0.0-beta4.22272.1) is highly extensible. In this blog post, I'll show you how to integrate true dependency injection using the official Microsoft.Extensions.DependencyInjection NuGet package.

IMO one of the best MVVM examples is Ambie, you can check it out.

Here's a few: - MVVM Toolkit sample app - Ambie - Brainf*ck# - DevToys

And for any devs out there, here's the source code: https://github.com/jenius-apps/ambie.

Not https://github.com/CommunityToolkit/dotnet

Here's some: - MVVM Toolkit - PolySharp - ComputeSharp

Started programming by writing some apps for Windows Phone later UWP during university. A few years ago I started collaborating a lot on GitHub to some Microsoft projects, like the Windows Community Toolkit. There I created a lot of new APIs and libraries, like all the new animation APIs and pipeline brush APIs, etc. I then also proposed adding some general .NET APIs to it, and that's how the MVVM Toolkit was born, along with other libraries which are now moved to the .NET Community Toolkit. Fast forward until about late 2020, and they pinged me saying the new Microsoft Store (which hadn't been announced yet back then) was using several of those new APIs I had written, so we started collaborating more so that I could add more functionality they needed. After that shipped, at some point there was a new opening to which I applied, and here I am in the Microsoft Store team and also leading the .NET Community Toolkit 🙂

This is tracked by https://github.com/CommunityToolkit/dotnet/issues/409. The issue is likely that AppCenter image using an older version of Visual Studio (and Roslyn). The MVVM Toolkit needs at least Roslyn 4.0 (ie. Visual Studio 2022) in order to work. Unfortunately this is not something we can change from the MVVM Toolkit, you have to open a support request for AppCenter to ask for a newer Roslyn version, or see if there is a way for you to enable that in your pipeline 🥲

The toolkit's:

https://github.com/CommunityToolkit/dotnet/issues/224 - one ask and fix.

Yeah, the fact properties use fields with annotations right now isn't ideal, it's just the best we could do until C# gets partial properties. I do plan on adding support for that though as soon as C# gets that feature. You can follow the progress here 🙂

For comparison, CommunityToolkit.Diagnostics has a guard library.

There is some stuff in CommunityToolkit to lower allocations of frequently converted Spans, StringPool comes to mind.

Most likely this: https://github.com/CommunityToolkit/dotnet/blob/main/src/CommunityToolkit.Mvvm/DependencyInjection/Ioc.cs