Handles the following issues:

- Correctly detect when an xunit run fails.  Previously only checking
the last run.
- Generate the xml results file for our xunit runs.  This will give us
better Jenkins output for cross plat runs.
- Disable a test which was failing due to the first issue I fixed.

Revert "Exclude transitive dependencies from vsixes."

This reverts commit 0eba2636.

Bring tie breaking rules around optional parameters and params parameters closer to native behavior.

Comment out the cross-langauge assembly load parts of perf tests.

Exclude transitive dependencies from vsixes.

disabled semantic version tracking.

current one is too fragile. just re-calculate it on new vs session

added explicit DocumentCloseAsync to IIncrementalAnalyzer so that re-analysis and close action have different behavior.

outcome of this change is that, when a user closes a document without saving, diagnostics will be cleared as expected.

current one is too fragile. just re-calculate it on new vs session

Bring tie breaking rules around optional parameters and params parameters closer to native behavior.

Fixes #2298.

added explict DocumentCloseAsync to incrementalAnalyzer so that re-analysis and close action have different behavior.

outcome of this change is that, when a user close a document without saving, diagnostics will be cleared as expected.

Fix issue #2130

We do not ignore it in "strict" mode.
This is a native compiler bug that we reproduce for compatibility.
Fixes #2249
Closes #2255

Use a recent Unicode version for case mapping by relying on a neutral culture

Change sibling check to use similarity instead of exact match

Serialize left out Shared Formatting Options

Fixes #2116, #620
See also #1070

Adjust constraints check for reduced extension methods to avoid failures for type parameters that couldn't be inferred from the first argument.

Extra ?. for safety

Extract method in Expression bodied members. Fixes #528

Updated - More use of nameof() operator in ArgumentException and derived classes

Switched from quoted argument names to nameof() operator, correcting a dozen or so in this manual process. RoslynLight.sln builds in VS2015 CTP6 and BuildAndTest.proj runs all tests without errors.

Note I did not update cases like: new ArgumentException("symbol") because according to the signature, the first parameter holds message and second holds parameter name. Not sure how the team would like to change this. Mostly affects code generated from Syntax.xml.

Adjust constraints check for reduced extension methods to avoid failures for type parameters that couldn’t be inferred from the first argument.

Fixes #2288.

#971 is now fixed, re-enable tests that were blocked on it.

Add support for extract method to work inside expression bodied members
and unit tests.

Fix #2218 : The Formatting Options UseTab, TabSize, IndentSize and
IndentStyle were not getting persisted. This change fixes it. The
integration tests will be added.

Fix a race condition in BatchFixAllProvider's merge logic, in presence of merge conflicts.

The current merge logic that merges code fixes from batch fixes ignores individual text changes that conflict with already merged batch fixes. This can be problematic if we have already merged a fix in the document in a later text span. We may end up adding text changes of kind Insert, but silently ignore text changes of kind Remove, returned by SyntaxTree.GetChanges(tree). This can cause the merged text document to be completely corrupt.
 Fix is to ignore all the text changes from a code fix (that is part of batch fixes) if any of its text change has a conflict.

NOTE: DotNetAnalyzers/StyleCopAnalyzers#723 represents another case similar to #463, where SyntaxTree.GetChanges returns an add + remove text change with long spans, when the actual text change is just a single char replace. This causes completely independent code fixes to seem as conflicting to the batch fixer. I'll file a separate issue for this API bug.

Fixes #320 

When classifying xml nodes in VB, use FullSpan

Since the editor calls us line by line, if we get called to classify a
comment trivia on the line before an xml node, we would not do so as part
of that line, because it doesn't overlap the Span. We would later do so,
but not actually return the spans to the editor, since they didn't
overlap the span requested.

Fixes #2126.

Moving CA1003 and CA2002 to System.Runtime.Analyzers

Add skipped test for another repro case for #463

Closes #1700.