referencesource

> It is also worth mentioning that the standard library implementation might change over time, which would break all past seeds. If the stdLib changes and you need to use the same, then you're unfortunately going to be suck with porting the previous version into your own library. It's pretty forward thinking from the devs here, I would love to see my boss' face if I told him we need time to port some of the stdLib incase they update it in the future. I had to check for my own curiosity, but it looks like the Random class has not been updated in 12 or so years. At least in the inital subset of framework to core. https://github.com/microsoft/referencesource/commits/main/ms...

The C# version will copy the list into an array during Task.WhenAll, it may save some memory to use an array directly. Souce: https://github.com/microsoft/referencesource/blob/master/msc...

The .NET source https://github.com/microsoft/referencesource https://github.com/microsoft/dotnet Unity reference source https://github.com/Unity-Technologies/UnityCsReference The above are example of production code. I use these as references all the time Awesome c# https://github.com/quozd/awesome-dotnet

There was an article ages ago I read about the rewrite of C#'s Dictionary to the new generic one that went from being reliant on allocations in the older releases (C# 1.0 didn't have generics so iirc it behaved more like Java's) to using a generic struct array. Doing so cut down the number of memory allocations to _3 allocations_ from something like _2 * N allocations_ (N being the number of elements in the map). The improvement in performance was apparently staggering when it came to lessening the GC pressure. (Sadly I couldn't find it with a quick google). https://github.com/microsoft/referencesource/blob/master/msc...

Of all things, VB.Net actually has a string reverse that handles unicode cases. I'm not quite sure how to view it in referencesource, but it is on Github. [1] The result is less than 100 lines of VB so I don't think it's -that- hard. There's certainly some clever index manipulation going on but nothing that looks too crazy. [1] - https://github.com/microsoft/referencesource/blob/master/Mic...

The .NET Framework is healthier than ever. Every revision since 4.5.2 follows the support lifecycle of the parent OS (which generally is much more than 3 years) .NET Framework has never had a license fee. An argument could be made that part of the cost of Windows OS is a .NET Framework licensing fee, but the fact is if you're developing for Framework then Windows is already in your purview. Admittedly, the .NET Framework is not open source. But a good amount of its source code is available for review: https://github.com/Microsoft/referencesource https://referencesource.microsoft.com/

Based on a very quick look at the source code here and the source code of System.String [1], it looks like the .NET implementation should be faster and more comprehensive. It would be interesting to see a deeper analysis and comparison of these two. [1]: https://github.com/Microsoft/referencesource/blob/master/msc...

The .Net Framework CANNOT be cross platform, it contains all of the Windows specific parts. The whole point of the .Net Core initiative is to pull out the OS agnostic parts and to rewrite other parts to be cross platform (e.g. A GDI-free System.Drawing[0]). The long term plan from what I've read is for .Net Core to eventually form the foundation of the .Net Framework, then the Framework (Windows/GDI+/COM+/etc) libraries with be built on top with other OS-specific libraries being created for other platforms. The vast majority of the .Net framework is already Open Source[1] including the compiler[2]. What in particular are you missing that you need? [0] https://blogs.msdn.microsoft.com/dotnet/2017/01/19/net-core-... [1] https://github.com/Microsoft/referencesource [2] https://github.com/dotnet/roslyn

The classic .NET framework is available at Reference Source: https://referencesource.microsoft.com/ https://github.com/Microsoft/referencesource It's under a proper Open Source license now too (the MIT license).

Yes, the code is MIT licensed. Check it on github: https://github.com/microsoft/referencesource In fact, for the past couple releases mono has replaced a lot of its library code with MS's quite successfully. Full disclosure - I run the mono team at Xamarin.

The referencesource project seems to be MIT licensed: https://github.com/Microsoft/referencesource/blob/master/LIC...