Don't restart on failed connection sequence

Port: Handle rename decl conflicts when decl file contains no refs

Handle out parameters in cross-language scenarios

Ignore the difference between ref and out in ```SymbolKey``` and
```SymbolEquivalenceComparer``` since two overloads cannot differ by only
RefKind.  This prevents VB FAR and GTD from being too discerning and
missing matching references.

Caveat: Switching between ```ref``` and ```out``` is still a rude edit, so EnC sets a
switch to force consideration of the difference.

Fixes #599.

Fixes #2352

This change fixes a rename crash that would occur when a method
declaration conflict was introduced in a file with no references to that
symbol, but where at least one other document in the same project had a
reference to that symbol.

When processing an individual project in ResolveConflictsAsync, we start
with the full set of documents from _documentsIdsToBeCheckedForConflict
related to that project. But, each rename phase can adjust this set of
documents (called documentIdsThatGetsAnnotatedAndRenamed locally) to
whatever documents are represented by the current set of
_conflictLocations, which can exclude the
_documentIdOfRenameSymbolDeclaration itself if it contains no
references. Now, when documentIdsThatGetsAnnotatedAndRenamed is
recalculated we make sure to keep the
_documentIdOfRenameSymbolDeclaration in the set if we're processing the
project that contains it.

The mapping to metadata should use the original anonymous type map, not the map translated to the previous generation

Avoid using GetEntireImage for detecting empty images as it maps the entire PE into memory in case of memory mapped PE image

Port: TypeInferrer: Infer types in collection initializers 

Remove superfluous sequence point emitted by VB await spiller

Add Roslyn to build task so GAC'ing isn't necessary for IDE.

Fixes internal TFS bug #529480

Normalize references to Microsoft.VisualStudio.Composition

Port: Don't assume rename text parses as IdentiferNameSyntax

Avoid using GetEntireImage for detecting empty images as it maps the entire PE into memory in case of memory mapped PE image

Introduce variable for an expression whose parent is a conditional access expression. Fixes internal bug 1130990.

Clone of approved PR: #2414

The mapping to metadata should use the original anonymous type map, not the map translated to the previous generation

This contains two small rename fixes related to invalid rename text:
1. In OnTextBufferChanged, we were trying to ensure that the
intersection of the tracked rename spans and buffer changes was a single
span. However, when the rename text is invalid, there can be many buffer
change spans that intersect a single tracked rename span, so we now use
the least bounding span of the resulting intersection. We maintain the
requirement that this bounding buffer change span intersect a single
tracked rename span.
2. When the rename text is invalid, we display it in the Rename
Dashboard. This change adds the same truncation algorithm already
applied to the original symbol name (which reduces it to 15 characters
and appends a "..." if necessary).

Fixes #1031

In both the C# and VB RenameRewriterLanguageServices, we were assuming
the new rename text would parse as an IdentifierNameSyntax, but if the
rename text is invalid it could parse as anything. For example, if the
user tries to rename "A" to "A.B", then it will parse as a
QualifiedNameSyntax. We now accommodate these cases.

Port VB filtering changes (#3088)

When sorting VB completion items, rank argument names lower than other matches. This matches the Dev12 behavior and fixes TFS 1155801.

Add a missing null check in UnboundIdentifiersDiagnosticAnalyzer.ConstructorDoesNotExist

Don't queue parse options compilation tracker action with possible partial semantics.

Make scanner resilient to binary files as input.

Jenkins cross platform updates

Fixing invalid cast when autoproperty is initialized in another initi…

changed error list to use SystemBrowser API from VS.

The compiler should not enter a passive shut down mode in the case where
a client connects and disconnects before it can send any request data.

This fix is a part of our AusGov perf work.  In that scenario we have a
high number of compilations running in parallel.  On medium sized
machines it is possible for the server to quickly become computation
bound and slow to respond to connection requests.  The client will break
off a connection attempt after one second and revert to a straight
command line build.

Before this change we would also restart the server in this case.  That
adds extra overhead because it will be restarted by a later client
request.  With this fix we just keep the server running in this
scenario.

The original intent of passive shut down was to handle Ctrl+C scenarios.
The user hits Ctrl+C and all computation should go away, including the
server.  A failed connection attempt shouldn't be treated as Ctrl+C.

Fixes #2867.

This changes our cross plat build to install the desired version of Mono
on the machine as a part of the CI process.  This lowers the management
overhead of our Mac / Linux machines as we can use any machine in the pool
vs. having reserved, and custom maintained, machines for Roslyn.

User scenario: IDE built-in analyzer UnboundIdentifiersDiagnosticAnalyzer throws a null reference exception and gets disabled with an exception diagnostic in the error list.

Fix description: Add a missing null check when computing arguments for object creation expression.

Fixes #3027

Testing done: Existing tests

this will let us use Edge browser in windows 10

changed sign method from vsix to vsixSHA2

Prevent spurious warnings about missing dependencies.

**Bug:** Fixes #3020.

**Customer Scenario**
1. User adds any analyzer assembly that includes a code fix to their project (e.g.,  Microsoft.CodeAnalysis.FxCopAnalyzers.dll or Microsoft.CodeAnalysis.CSharp.FxCopAnalyzers.dll).
2. Users saves their project and restarts VS.
3. User reopens the same project.
4. User gets spurious warnings about 'System.Composition.AttributedModel' not being found and analyzers possibly not working. Closing and reopening the project sometimes helps, but more often than not the warnings show up.

**Fix Description**
The fix updates the `AnalyzerDependencyChecker` to allow whitelisting arbitrary sets of assemblies, not just those already loaded. This is used to then whitelist all assemblies with a name starting with "System" on the assumption that even if they are not already loaded they will in fact be found if needed. If an analyzer reference appears on any whitelist we won't report it as missing, even if we don't know where it is.

**Testing**
I tested the customer scenario listed above, and also tested that missing assemblies that *don't* start with 'System' as still reported.

Respect ParamArray attribute in source on a delegate parameter.