Fix VisualBasicSettingsManagerOptionSerializer.GetStorageKeyForOption so that we handle ServiceFeatureOnOffOptions.OptionName separately.

We didn't implement the old, internal, legacy `IParameterKind` interface on `EnvDTE.CodeParameter` because much of the information provided by this interface was included in `EnvDTE80.CodeParameter2` back in Visual Studio 2005. However, it turns out that there is some old code in the V1 Windows Workflow designer that depends on `IParameterKind` being implemented. This change adds support for `IParameterKind` to `EnvDTE.CodeParameter` and implementations for two members: `GetParameterPassingMode(...)` and `SetParameterPassingMode(...)`.

This brought along some references to Microsoft.VisualStudio.Threading
that we previously didn't have. Nothing was wrong with this, but it
meant I had to fix some namespace qualifications that were assuming the
"Threading" namespace was unambiguous.

This fixes the ability to build with later versions of Visual Studio
on your machine, since some later versions are incorrectly embedding
type forwards to assemblies that they shouldn't be. The NuGet package
includes dependencies of

- Microsoft.VisualStudio.OLE.Interop
- Microsoft.VisualStudio.Shell.Interop
- Microsoft.VisualStudio.TextManager.Interop
- Microsoft.VisualStudio.Shell.Immutable.11.0

automatically, and so I remove those from the project files now too.

If we don't have this, CreatePkgDef is getting angry. My guess is the
assembly is no longer in the GAC, and so it's being implicitly relied on
that the assembly is copied by MSBuild for CreatePkgDef to find it.

For the Shell binary, we have two choices. We could either reference the
version that matches the version of Visual Studio you are building with,
or we could reference a fixed version with a HintPath so we can find the
binary on all versions of Visual Studio. Doing the former is tricky
since the name of the assembly is embedded into some XAML, so I go with
the latter option.

Now that we run restore again on our Windows build machines, we can
delete the checked in files for projects only needed for the Windows
build.

Revert "Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results.""

Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results."

AbstractProject had two properties: Workspace and VisualStudioWorkspace
which was very, very confusing. We reduce down to one, and the few
places that needed the derived types

Our previous heuristic is we tracked any document that had a moniker
that wasn't contained within any project in VisualStudioWorkspace.
This was implemented with a private hook between the two systems. This
blows up in the face of other parties wishing to create their own
workspaces against files in the RDT, since we stomp on them. The new
heuristic is we attach to any file that's open and doesn't already have
a workspace, and we watch for registration changes to back off if
something else has taken a file.

Fixes #8598.

This reverts commit 760e1204.

this should make roslyn to turn off full project diagnostics when intellisense build is failed for the project.

when we detect intellisense build failure, VS should put actionable data in error list detail pane.
also bing search for the issue should work as well if one prefer blogs.

this change also fix some issue on cross language p2p references. before there was case where we fail to connect cross language p2p reference causing a lot of errors.

this change also include bulk diagnostic update events improvement. this should let us to deal better (especially when we clean those up) when there are a lot of diagnostics.

This reverts commit e2fc5135.

This reverts commit 8f26ffb5.

Synchronize all corefx references to -23504 and bring in the
xunit coreclr test runner.

This adds support for a new ICompilerOptionsHostObject which is how we
can pass options through the project system without having to manually
add separate properties for everything as we've traditionally done in
the past. To ensure compatibility with "new" compiler tasks against
"old" project systems, and "new" project systems against "old" tasks, we
continue to use the historical ICscHostObject* and IVbcHostObject*
properties for all existing values, and only use this property to
shuttle through new values. For the rest of Visual Studio 2015, we can
just use this for any new "simple" switches that we must pass along.  We
still would need to do additional work in the project system for any
inputs that are lists of files because of the fast-up-to-date check.

Longer term, there is still the unanswered question of how we want to
future versions of Visual Studio to get command line options to
completely get rid of all language service knowledge of this. There are
two possible approaches:

1. We just use the support added in #4604 and just delete this entirely.

2. We continue to use ICompilerOptionsHostObject. My proposal for that
   would be we continue to use the model of "we pass all options not
   supported by a strongly typed host object interface to
   ICompilerOptionsHostObject", and the project
   system would just remove all support for everything else and
   fail those QueryInterface calls.

This is therefore written with the idea that we could switch to option 2
in a coordinated way, if we wanted to do so.

Fixes #7812, assuming you have an updated csproj.dll and msvbprj.dll
which understands the new ICompilerOptionsHostObject.

The type is about to do more than just Edit and Continue!

It really had nothing to do with analyze rules, but was just a generic
mechanism for the base type to signal to derived types it needed a
refresh of the compile options. Since having a single entry point for
that is nice anyways, I rename it and promote it. I also make it
abstract because it was very unclear why the derived types were
calling the base type and what the contract might be for that.

Changes behavior of send to REPL when no selection is present.
In this case selects the line under caret.
When this line is invalid syntactically expands the selection to a valid
parent syntax node.