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.

...the same way we expand display classes and state machines.  If we see a
local or parameter with a transparent identifier generated/mangled name,
we should instead include the properties of its (anonymous) type in our
list of bindable symbols.

This is a port of ec4d462d

There is one notable difference between C# and VB: whereas C# has a
single mangled name for transparent identifiers, VB has four - $VB$It,
$VB$It1, $VB$It2, and $VB$ItAnonymous.  Fortunately, the differences are
not interesting to the EE - they're only to prevent name collisions
(except $VB$ItAnonymous which is used when the value is not an anonymous
type and does not need to be expanded).

This deletes the empty and unused Desktop assemblies from the code base.

Centralized some of our scattered uses of reflection to PortableShim.
While moving I verified all of the APIs are a part of the CoreFX +
Portable plan.

This removes the majority of references to the deprecated Desktop
assemblies.  The only remaining ones are in the VSIX projects.  They
must remain until we actually delete the assemblies.

Fixes #2604.

This moves the contents of the CSharp and Visual Basic Desktop
Projects to the Portable counterparts.

closes #2587

VB EnC: when lowering conditional branches produce a pattern that allows the debugger to perform function remapping

Remove explicit references to System.Reflection.Metadata and System.Collections.Immutable from project-level packages.config

Enable Conditional Access optimizations for cases when LocalRewriter introduces a local in the process of initial lowering of the access.

Fixed #2424.

This test was disabled due to an issue running the test on CTP6.  This issue no longer reproduces on
newer builds including the RC.  Enabling and closing the bug.

closes #856

The old fix used SpecialType decoding to fetch the unified special type
for the encoded type of a FixedBufferAttribute. While this works, the
underlying issue behind the missing type inside the FixedBufferAttribute
is that decoded types are loaded by checking the referenced assembly symbols
rather than the referenced assemblies.

This reverts the change from d4a181 and changes type decoding in
attribute loading to use the referenced assemblies.

Add unit-tests to ensure that unterminated element in XML Doc comment doesn’t cause compilation failure.

Fixes #2371.

Fixes #564

sequence of operations to the PDB writing library
Fixes #926
Closes #2342

This change enables the C# Semantic and Symbol suites.

Fixes #2349.

Created a cross platform solution

This solution file contains the set of projects which we support
building cross platform.

Note: ideally this would be the same as Toolset.sln.  However there are
certain dependencies which we simply can’t use cross platform at the
moment (MSBuild in particular).  Eventually these two solutions should
converge if possible.

Fix stack overflows when running in Mono

Several of our test suites have cycles between static field
initializers and the containing types constructor.  The mono runtime
ends up stack overflowing on these cycles and prevents us from running
suites.  Changing the suites to remove this cycle via lazy field
initialization.

Fixes #2116, #620
See also #1070