Conflicts:
	src/Workspaces/Core/Portable/Rename/ConflictEngine/ConflictResolver.Session.cs

Report CS0513 for abstract declaration

AssemblyLoader and ScriptBuilder cleanup

Add history navigation and search tests

Disable refactorings in the Interactive window

Fix codegen for integral switches with only null and default cases.

Get document moniker from IVsProject instead of RDT

Update System.Reflection.Metadata to -0014

Add a new analyzer and code-fix to detect and recommend when people can use the auto-property pattern.

i.e. if yo have:

```c#
class C {
  int i;
  int P { get { return i; } set { i = value; } }
}
```

It will fade out ```int i;``` and offer to fix the code into:

```c#
class C {
  int P { get; set; }
}
```

Add exception filters to get better crash dump for exceptions during conflict resolution

We were forgetting to emit a branch to the fallthrough case.
Normally emitting the jump table would do it, but in a case where the only nondefault label is the null label, no jump table is emitted.

Fixes #4701

Pay attention to sizes and lower bounds specified for multi-dimensional arrays in metadata signatures.

Add CscCore to CrossPlatform.sln

Make NuGet sources more deterministic

Async loading with property pages

If we failed to get a document moniker for the contained document, fail
now.  Otherwise we'd crash when attempting to create a document key.

Switching to IVsProject.GetMkDocument to get document moniker instead of
iterating through all the entries in the running object table. Also
cleaning up a bit of code while I'm here - It looks like we don't need
to determine Shared Hierarchy & Shared ItemId here anymore. It was there
for error list and it looks like with PR #2399 error list switched to a
different implementation.

Updates the mono toolset to mono built from source at tag
mono-4.2.0.207.

Updates the mono toolset to mono built from source at tag 4.2.0-207.

This is needed to unblock the core change to fix issue #4183.

project.json Fixes

Added a clear entry to our package sources to ensure builds on developer machines weren't inadvertently affected by local settings.

Pay attention to sizes and lower bounds specified for multi-dimensional arrays in metadata signatures.

Fixes #4954.

We will treat Sizes and LowerBounds similar to custom modifiers. They should match for the purpose
of signature comparison (overriding/implementing, etc), but shouldn't affect conversions.