Fixes #8452

Improve selection handling when sending to interactive

Changes needed to create a F# language service based on Roslyn workspace model 

Reduce VM usage for RPS tests by using a special back-door interface to mark analyzer as needing less work.

Fix bug in IVsSimpleLibrary2.CreateNavInfo(...) implementation where we were clearing string builders before they were used

Update Roslyn to DSR v1.0.7 release

Only move the caret if the enter was hit within the snippet fields.

Verify that bound node has ConstantValue even when underlying symbol has one.

Fix bug in IVsSimpleLibrary2.CreateNavInfo(...) implementation where we were clearing string builders before they were used

Fix params array argument operation

Fix #7867: Improve documentation of Diagnostic.Create properties argument

make msbuildtask not eat errors

Enable interactive commands

Base selection on the currently opened Document

Use 'nameof()' in places where we were initializing a variable with the string form of its name.

Run codeformatter on our code.

fix crash.

Archive only relevant artifacts

Also address code review comments.

Handle ErrorTypeSymbol as a ContainingSymbol of TypeParameterSymbol in CSharp.DocumentationCommentIDVisitor.PartVisitor.VisitTypeParameter.

Enable execute in interactive command.
Enable reset interactive from project command.

Adjust the Portable PDB validation code to account for missing VB fake locals

Fixed #8475.

Fix and enable failing C# xplat syntax tests

Change our archive logic to only store the items that we actually use for investigations.

closes #8550

Code Model: Don't crash when adding element, deleting its text and then adding it again

use FormattedSymbol

Enable parallel runs of determinism job

I don't have heap so can't figure out why the situation happened. but this should at least prevent crash.

when this happens, after this fix, we might have wrong span for diagnostic, but that is not critical issue to crash VS.

The bug causes the Syntax for a IArgument of Paramsarray kind
with only one element to be null.

In the initial move to running tests xplat, a number of tests were
disabled due to failures in xplat CI. Some of these failures are
inherent platform limitations, like tests which depend on the Windows
.NET Desktop framework, but some were simply improperly written tests.

This change re-enables and fixes the tests that were improperly or
non-portably written.