In MSBuildWorkspaceProjectLoader, there is a map of "discovered" projects that stores the results of any project references. If a
project reference can't be loaded (for example, because it is a reference to, say, an F# project), it can end up in the map twice if the
project referencing it is multi-targeted. For example, a multi-targeted C# project that references an F# project will fail when loaded
because the path to the F# project will get added twice with an empty array of ProjectInfos. The reason for this is that the code assumes
that the loaded project will end up in the primary loaded project map, but in this case, the project couldn't be loaded and isn't there. To
avoid this situation, we call TryGetValue on the "discovered" projects map and return the results before trying to load the project again.

Added AddMissingImport CodeRefactoring driven by PasteTrackingService

Added PasteTrackingService that handles the paste command and track
paste information for documents. This paste information can be used
by refactorings to make suggestions based on what was pasted.

Fixes #10272

Do not remove parentheses from incomplete expressions

Update to vs-threading analyzers 15.8.168

See #30264

Report AD0001 if an analyzer accidentally provides a null descriptor …

Fix symbol end action not completing for symbols with non-implicit me…

Fixes for integration tests

Merge range to dev16.0.x

Fixes #30453

Fix for Incorrect IDE0052 (assigned but never read)

Bring ranges up to date

Add a unit test for the failing scenario. Verified the assert fires prior to the fix for the added unit test and the unit test fails.

Added DotNet global tool for code formatting.

Tool can be run on a project, solution, or folder containing a
project or solution. Tool pulls formatting configuration from an
.editorconfig if present, otherwise formats with roslyn defaults.

Handle failures during integration test remoting cleanup

Fix race condition in symbol start action execution

Add an explanatory comment and revert the semantics of the new TestParameters flag so the default value (false) retains the current semantics.

Fix failure to close the C# Interactive window in tests

* Change Windows build machine affinity to Windows.10.Amd64.ClientRS3.DevEx.Open

These machines have .NET Framework 4.7.2


(cherry picked from commit 416f5304)

Skip M.CA.CS.Symbol.UnitTests on dev16.0.x

Enable testing non-fixable diagnostics in the test framework. Current implementation filters out all non-fixable diagnostics completely.