dotnet VS referencesource

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

But to go deeper to .NET/CLR architecture is important too. Try to understand how it works inside. Use the source, Luke! https://source.dot.net/ https://referencesource.microsoft.com/ This source code vaults is not completed then try JetBrains dotPeek tool to look at any assembly source code.

(https://github.com/Microsoft/referencesource/blob/master/System.ServiceModel/System/ServiceModel/MessageSecurityVersion.cs; scroll down to inner classes)

List is an IList/IReadOnlyList; these interfaces do nothing that couldn't be done right inside the file itself.

https://referencesource.microsoft.com/#mscorlib/system/colle...

https://referencesource.microsoft.com/#mscorlib/system/colle...

Instead we have to go diving through the IList, which implements ICollection, which implements IEnumerable, which implements IEnumerable (again). Just because each interface is composed of another interface, doesn't mean you aren't using inheritance. You are effectively creating a custom inheritance tree through willy-nilly composition.

It is gratuitous to make this chain so deep, when the underlying code is just a handful of lines.

https://referencesource.microsoft.com/#mscorlib/system/colle...

https://referencesource.microsoft.com/#mscorlib/system/colle...

https://referencesource.microsoft.com/#mscorlib/system/colle...

----------------------------------------------------------------------------------------------------------------

The doc-strings are unnecessary. It's self-evident what most of the code does if you read it.

        // Returns an enumerator for this list with the given

The whole .net framework source code is online.

https://github.com/microsoft/referencesource/blob/master/System.Numerics/System/Numerics/Vector2.cs https://github.com/microsoft/referencesource/blob/master/System.Numerics/System/Numerics/Vector2_Intrinsics.cs

.net itself has arbitrary interfaces, ex https://github.com/microsoft/referencesource/blob/master/mscorlib/system/action.cs

Assuming if you are new to C# - start coding! And start reading https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csha...

If you are not new to C#, start building an application end-to-end/a classic n-tier application, right from using a database, Entity Framework, WebAPI, DTO, AutoMapper, and a front-end (your choice - Angular/React/Vue with TypeScript or better yet - Blazor).

You will not only understand & use dependency injection, reflection, LINQ, multi-threaded programming, generic programming, source-code generation, unit-testing - and much much more in a practical/real-world usage.

Peruse https://referencesource.microsoft.com/ once in a while.

Follow various team members of .NET Framework, C# team and the like on various social-media. https://mobile.twitter.com/i/lists/120961876

I am sure there will be who agree / disagree with the above approach and will provide more viewpoints for you to consider.

Enjoy - and strap yourself for an amazing journey or roller-coaster ride, however you want to call it!

Maybe from the source of FtpWebRequest it is possible to track what the default behaviour is.

The class is just a very limited dictionary, a library will be the same or better.