Report errors and exceptions from source generators

Updating the InteractiveWindow ClipboardTests to match the expected clipboard format in Update 3.

Updating our jobs to use the VS2015.3 image.

Fix tests in PatternMatchingTests that fails in cultures with differe…

* Comments on perf test

* address feedback

* fixed spacing issues

Update SRM to 1.4.1-beta-24227-04

Readme updates

Now that Visual Studio 2015 Update 3 has shipped, this branch is dead.

* add flag for specifying trace upload location

* start porting the command line parser

* finish mono option parsing

* switch to project.json

* stash

* added project.json

* disable signing

Fixes #2983

Adjust more places outside of compiler to account for the fact that ArgumentSyntax.Expression can be null.

Fix PublicKeyToken used for framework references

These are built with the core framework key, not the key Roslyn uses.

Adjust more places outside of compiler to account for the fact that ArgumentSyntax.Expression can be null.

TS has moved to newly added APIs, so remove the old APIs.
Fixes #11501

It's not unusual for a user to accidentally place an accessibility
modifier on a local function declaration, but currently visibility
modifiers are not seen as possible starts to statements, so parsing
falls back to member parsing, assuming that the user forgot a closing
brace on their method. This PR changes parsing to allow local function
parsing to eat a visibility modifier and report an error. If parsing
doesn't find a local function after the visibility it falls back to the
old interpretation (that the user forgot a closing brace on their
method) and treats the modifier as the start of a new member.

In the case where it's ambiguous between a new member with a missing
closing brace and a broken local function we assume that it's a broken
local function. Fixes #8645.

Debug updated parameter in Closure in statemachine

* Display analyzer assemblies with no applicable diagnostic analyzers towards the end of analyzers list in solution explorer

For most cases, these are analyzer depedencies with no analyzers.
For few cases, these might be analyzer assemblies with no analyzers applicable for the given project langauge.
For few other cases these might be analyzer assemblies whose diagnostic analyzers could not be instantiated for some reason, and hence have no rules.

We still display such analyzers in the solution explorer so the user is aware that the project file contains these analyzer references, but display them towards the end to avoid clutter.

Fixes https://github.com/dotnet/roslyn/issues/12047

* Address PR feedback and completely hide the analyzer dependencies (analyzer assembly has no diagnostic analzyers and also has no load errors)

Update to DSR 1.1.0-beta1-60617-01

Fixes #11442

Add unit-tests for issues #12058 and #12182.

Merge current microupdate fixes back into master

fixed 2 memory leaks

Only compute entry points when compiling everything.

Add test to ensure that a CompletionService can be acquired

Issue #11841 found that, due to a MEF bug, the Features assemblies could not properly be included in a MEF composition. This was worked around by combining [ExtensionOrder] attributes where multiple attributes had been specified. This change adds a tests for C# and VB to ensure that a CompletionService can be acquired from an AdhocWorkspace that is created with MefHostServices that include the Features assemblies.

I verified that these tests fail without the workaound described above, and pass with the workaround in place.

MEF has issues with duplicate attributes.