Fix Interactive window indentation

disable loaded dlls checking

it looks like loaded dlls checking action is broken. when it says wrong dlls are loaded, windbg doesn't agree.

The value returned from
```ISmartIndentationService.GetDesiredIndentation``` is absolute, but we
were assuming it was relevant to the prompt.

Fixes #4235

Loosen diagnostics assert

Don't crash when invoking signature help on an inaccessible item.

When gathering symbols for invocation expression signature help, consider the left expression explicitly, not just by name

Add spacing rules around Dictionary Initializers

This reverts the workaround made in fcc26eab. The actual issue was fixed with 0d99437e.

Unblocking the ability to run Unit Tests locally.

This updates the referenced version of 'Microsoft.CodeAnalysis.Test.Resources.Proprietary' from nuget 20150716.7 (20150716.5 and 20150716.6 are also broken) to 20150717.8, which contains the actually signed binary.

Fix customer tests

The Microsoft.CodeAnalysis.Test.Resources.Proprietary package is not properly signed
on NuGet.  This breaks test runs on standard machines (where signing verification is
still enabled).  As a temporary work around fake sign the binary during a test
run.

Protect against nulls in EquatableAnalyzer and add unit tests

Fix #4280 Add spacing rules around the dictionary initializers to have a
behavior similar to Object Initializers

Fix issue where asking the solution crawler to reanalyze projects was a no-op.

Unblock running unit tests

Update portions of Crypto loading

Nuget package
Roslyn sources depend on
Microsoft.CodeAnalysis.Test.Resources.Proprietary.1.1.0-beta1-20150716-05
which was not signed, so running tests was broken. I've uploaded a newer
package `07` to nuget.org that fixes the problem. This PR updates the
package references in Roslyn source to consume and build using the newer
package.

don't escape method names in signature help tool tips

Fix VB member body span used to determine whether speculative binding should be used

All tagger changes including diagnostics.

Fixing the versioning and hint paths to be configuration/version independent.

No longer mark text buffers as user-readonly

Rename pkgdef used by Interactive...

DiagnosticIncrementalAnalyzer.LatestDiagnosticsForSpanGetter.VerifyDiagnostics
checks that the diagnostics returned by the SemanticModel for a given span
are the same as the diagnostics returned by the SemanticModel for the
whole document after filtering down to the span.  This check fails when
the span includes unused import diagnostics, because they are never
reported by the SemanticModel when a (sub)span is given.

Fixing a bad hint path.

...so it doesn't conflict with the one used by the "normal" language
service.

C# SemanticModel.GetSymbolInfo - Properly handle explicit method group conversions.

This fixes a bad hint path in BasicCompilerEmitTest.vbproj

This

To determine whether or not speculative binding should be used, GetSemanticModelForSpanAsync calls into ISyntaxFactsService.GetMemberBodySpanForSpeculativeBinding(). In VB, the span returned by this method started from the end of the block statement to the start of the end block statement. However, for VB, the span should start after the block statement's terminator. Otherwise, a member body speculative semantic model will likey be returned when the requested span is within the trivia after the block statement but before the statement terminator. E.g.

Sub M() |

End Sub

Fixes #3096.

Revert "Update the XUnit runners to support CoreCLR"