Add a new command line compiler switch "/reportanalyzer" to report analyzer execution times. Output is grouped by analyzer assemblies and is displayed in descending order of execution times.

NOTE: We do not display the total build time or the ratios between build time and analyzer execution time as the the actual wall clock time for analyzer execution is likely lesser due to multithreaded analyzer execution.

Rationalize Code Model "member node" logic

Revert change to VS Setup to include the build task

Code Model has several ways of looking at the member nodes of a
particular container. Sometimes it does so recursively, flattening all
nested members into a single list. Sometimes, it looks for "logical"
nodes, i.e. breaking up field declarations into their component
declarators. Sometimes only supported nodes (that is, nodes that can be
properly represented in Code Mode) are expected.

Unfortunately, the internal APIs for these searches grew up organically
and have ecome quite a mess. There were several places where the wrong
search was being used, resulting in strange bugs*.

These concepts are now consolidated into a single GetMemberNodes()
method and all callsites have been reviewed and updated.

* The particular bug that this change addresses is about inserting a
node into a container that contains an incomplete member. In that case,
the code used a "flattened" list to find the index where the node was to
be inserted. What it really wanted was a "logical" list, but that was
conflated with "flattening".

Update toolset compilers and analyzers.

Update to version 1.0.0-rc3-20150510-01.

add base list before trailing trivia

moved tableControl APIs to the new ones

Fix incorrect usage of string.Format(...) in analyzers.

This change fixes up a few places where we're using `string.Format(...)` when creating a `Diagnostic`  in order to vary the message, rather than creating multiple `DiagnosticDescriptors`, each with a different message.

This worked fine for English but probably would have fallen down when trying to use localized strings. The whole point of a `LocalizableString` is to capture enough
information such that the string can be rendered into an arbitrary
locale at a later time; by using `string.Format(...)` we were tying
ourselves to whatever the `ResourceManager` decided was the right locale
to use when the `Diagnostic` was created. This may not be the same
locale that we would pick when actually showing the message to the user.

The fix here is to create multiple `DiagnosticDescriptors` that just happen to have everything in common but the message format.

removed unused using and use ProjectGuid from editor rather than defining our own since we have new bits now

Fix simplifier bug around paren removal

Trivial temporary storage

Fix rule set rename issues.

Currently, if a .ruleset file is renamed, deleted, or removed, we only
update the `CodeAnalysisRuleSet` property on projects that included the
.ruleset as a project item. This commit institutes better rules:

* If a project- or solution-level .ruleset is renamed, we need to update
every `CodeAnalysisRuleSet` property containing the old name in every C#
and VB project--even if the .ruleset isn't a file in the project.
* If a project- or solution-level .ruleset is deleted, we need to clear
every `CodeAnalysisRuleSet` property containing the name in every C# and
VB project--again, even if the .ruleset isn't a file in the project.
* If a project-level .ruleset is removed, we only clear the
`CodeAnalysisRuleSet` properties for that project.
* If a solution-level .ruleset is removed, we do nothing.

Note that only some of these operations are currently possible within VS. For example, you can't rename a linked file, nor can you delete a solution-level file--only remove it from the solution.

Fixes #1601.

Disable Rename Tracking with "var" and "dynamic" in C#

Make constructors of FixAllContext public.
This unblocks a few product/test FixAll scenarios, see #2709 for details.

C#: Mark return value synthesized local as long-lived

Simplifier should not remove parens around ConditionalAccessExpressions that are inside MemberAccessExpressions since this changes semantics.

Fixes #2211

Fixes CultureInfo light-up code

Add regression tests for #2614. The issue doesn't seem to repro on latest Roslyn bits.

Make constructors of FixAllContext public and add a new nested abstract public type "FixAllContext.DiagnosticProvider" for fix all diagnostic queries.

This unblocks a few product/test FixAll scenarios, see #2709 for details.

Do not allow await in catch/finally in language version 5

Explicitly reference all nuget package versions as build properties

Pass correct context type to runtime binder

Use correct properties collection for msbuild

Fixes #2725