Balkoth

Another blog post dropped: https://devblogs.microsoft.com/dotnet/binaryformatter-removed-from-dotnet-9/ How is this project going to resolve this. Are users now expected to use an unsafe and unsupported library? .NET BlogBinaryFormatter removed from .NET 9...

I guessed that too after i filed the issues and created the pull requests. Imho the methods definitions should be ifdefd for the correct platforms, then there would be no...

I guess that is open for discussion, but it was allowed previuosly and i would consider this a change now, when it warns, when it is valid to have null...

Just some food for thought: ```cs List objects = new List(); objects.Add(new object()); objects.Add(null); AdvancedCollectionView acv = new AdvancedCollectionView(objects); ``` This code is also perfectly valid and no warnings are...

I was updating my generated client this morning with the latest kiota bits and came to a similar conclusion as @0xced. The code now looks ugly. At first, i thought...

This is what it looks like after double clicking `System.CommandLine.sln` from explorer, so it is already there:

No, this does not matter. What matters on my dev machine is when i start Visual Studio with an admin account. Then it suddenly can open those projects and does...

I am using the official [contribution](https://github.com/dotnet/command-line-api/blob/main/CONTRIBUTING.md) documentation, there is no such info to run Visual Studio as administrator. And btw you are mixing running command line commands with Visual Studio....

Two things need to be done in order to successfully load and build the projects: - Set environment variable `DisableArcade` to `1` - Delete `NuGet.config` from the root directory

I believe we can agree that the goal should be: - Read and follow the steps in [CONTRIBUTING.md](https://github.com/dotnet/command-line-api/blob/main/CONTRIBUTING.md) - Be able to open and build the solution in Visual Studio...