visualstudio-docs VS ReferenceAssemblyAnnotator

I created VS solution with an asp.net core backend and React frontend as separate projects following this tutorial/template. It's an old GitHub link because I created the project before the official page was updated.

There are some hints in this document, like the OS needing to lock down installed app files:

https://learn.microsoft.com/en-us/windows/msix/desktop/deskt...

Or this issue: https://github.com/MicrosoftDocs/visualstudio-docs/issues/33...

Microsoft C++ Style Guide Example

I opened an issue in Github. You can see the answer I got: https://github.com/MicrosoftDocs/visualstudio-docs/issues/8404

It should work for .net framework as well, check out https://github.com/MicrosoftDocs/visualstudio-docs/issues/5291. As per UI way, you've demonstrated it to us in your question :) Click on "Why can't I select a different C# version?" and read through.

For example to debug a multithreaded application you have these kind of things https://github.com/MicrosoftDocs/visualstudio-docs/blob/main/docs/debugger/walkthrough-debugging-a-parallel-application.md

Did you go for the "install while downloading" option? You can try a full download instead: https://github.com/MicrosoftDocs/visualstudio-docs/blob/main/docs/install/create-an-offline-installation-of-visual-studio.md

https://github.com/manuelroemer/Nullable (backport nullable attributes so you can use things like [NotNullWhen]). Alternatively, https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator/ is even niftier, as it gives you .NET 5's annotations as well. So the compiler tells you whether a Dictionary.TryGetValue result is nullable or not based on annotations that didn't exist in .NET Standard 2.0.

If you need the attributes, reference https://github.com/manuelroemer/Nullable or https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator. The latter is bigger, but retroactively adds nullability annotations to runtime references (such as Dictionary.TryGetValue).

EDIT: A reader reached me about this cool package that partially solves this problem by injecting nullable reference type annotations in CLR's methods of some assemblies (check the docs for more details): ReferenceAssemblyAnnotator.

This helps: https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator

Can't use 6.0 on that solution because https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator/issues/89. But I did try 6.0 on a smaller project, where indeed, the warning seems to only appear if I downgrade to the 5.0.400 SDK. With 6.0.400, I get… a build error instead. With that workaround, it works.

https://github.com/tunnelvisionlabs/ReferenceAssemblyAnnotator to get Nullable Reference Type annotations from .NET 5 backported to Fx