This behaves more or less exactly the same as IGoToDefinitionService.

This requires some updated handling of our INavigableItem interface.
The Visual Studio implementation previously would only show the
DisplayString if it had children, and would otherwise show file
location and the source snippet. For implementations, the source
snippet is somewhat useless: in the case of methods you just see
the method signature a bunch of times. Thus, we wanted to show source
location and a fully qualified name, something which wasn't expressible.

The new interface now has DisplayString, which can be null if you want
the string to be line from the source. Whether you want to show the file
location is explicitly called out now too.

It can contain modifiers or other things, so it's not just a name.

Our INotificationService took a title and a message. In VS, the title
and message were just concatenated together on consecutive lines and
both displayed in the "message" portion of the message box. In other
hosts, we used the title as the "real" message box title. Features
were terribly inconsistent with how this was handled. Some features
expected the VS behavior (and would have had clipped text in other
hosts). Other features didn't expect the VS behavior, making ugly
dialogs.

The new behavior: the title is reserved for the title bar. This is
ignored for the VS implementation, but should just be (if anything)
the name of the feature complaining about something. All features who
actually wanted the concatenation behavior are now doing so explicitly.

TryGoToDefinition accepted a containingTypeSymbol which was used
to do some specific logic to see if third-party navigation is allowed.
Move that logic to the AbstractGoToDefinitionService and just pass the
result of the logic through.

Fix issue when pressing ENTER in XML doc comments with a selection

In order to insert XML doc comment exterior trivia (e.g. /// or '''), we grab the caret position prior to the new line being inserted into the editor and then perform a bit of analysis afterward using that position. However, if there's a selection in the editor and the caret is at the end of that selection, the position will be in an unexpected place in the syntax tree, causing that bit of analysis to fail. So, in this case (and all cases), we use the start of the selection as the position to perform analysis on since that position will be consistent after the new line is inserted.

made InternalsVisibleToMoq item hidden in solution explorer

fixed race in task providers

Show property accessor accessibility in CSharp QuickInfo

Add a server mutex to VBCSCompiler

Remove dogfood configurations

Fix mixed encoding

Issue #2790 describes multiple servers running with the same pipename,
which should never happen. It's probable that this was caused by the
File.Exists line in #3177. This change adopts a different strategy
than attempting to check for the existence of the pipe -- instead we
use both client and server mutexes. The client mutex prevents multiple
clients from trying to start multiple servers simultaneously, while the
server mutex acts as a signal to the client that a server is already
running and a signal to all servers unable to grab the mutex that they
should shut down.

As always, any failed server usage simply results in the use of the
in-proc compiler.

Fixes #2790,#3177

Stop setting InternalFeatureOnOffOptions

Change Windows command line argument parsing

Allow #r package reference without explicit version

Minor code cleanup

Add null checks for #load'ed trees...

Reduce VBCSCompiler polling frequency to 1Hz

Add a separate package for the Linux coreclr runtime

Add regression tests for interactive using bugs

...to work around machines that already have the old option set.

Make InteractiveWindow use HACK_ThemeColorFixer

Fix function pointer representation