turn on esent only on a large solution. otherwise, just hold everything ...

add unit test for build zero length squiggle change

make only live diagnostic's squiggle to be minimum length of 1

# The first commit's message is:
Move csc2/vbc2 logic into csc/vbc behind '/shared' flag

This change adds support for the '/shared' flag to csc/vbc, which indicates
to the command line compiler that it should attempt to use the compiler server.

This change doesn't yet delete the csc2 and vbc2 binaries to preserve compatibility
for our partners until they have a change to switch to the new API.

# The 2nd commit message will be skipped:

#	Address CR comments

# The 3rd commit message will be skipped:

#	More CR comments

threshold to turn on esent is 50MB > solution source size. esent will be turned on dynamically, once turned on, it will turned off again when solution is closed.

this PR addresses #910

Produce 'invisible' squiggles for 'Remove Unnecessary Usings' and 'Simpl...

other ones such as build will have minimum length of 0 for squiggles since they are not updated as your types. minimum length of 1 for such squiggle just makes it look like staled squiggles.

Produce invisible / suggestion squiggles (which will in turn display Quick Info on mouse hover) for the hidden diagnostics that we report for 'Remove Unnecessary Usings' and 'Simplify Type Name'. The presence of Quick Info pane for such squiggles allows allows platform to display Light Bulb for the corresponding fixes. Per their current design platform can only display light bulb if Quick Info pane is present.

Load analyzer satellite assemblies

Use ISymUnmanaged* from Microsoft.DiaSymReader

replace ShimTable to StandardTable before error api cleanup from API nam...

Consider MVID when testing EC cache validity

Also removes obsolete settings for the Csc/VbcToolTask properties
which would prevent us from using the task ToolTask property to
see if we want to use a different tool exe.

Our EvaluationContext cache invalidation computation was consuming the
method token and version, but not the identity of the declaring assembly.
This lead to a strange bug where we would reuse the cache across assembly
boundaries if consecutive breakpoint happened to have the same method
token (each in its own assembly).

I believe this bug existed before I revised the cache invalidation
computation and we were just getting lucky - we used to check the spans
of all containing scopes, which are unlikely to match exactly across
assemblies.

there is API cleanup going on and they are removing ShimTable APIs.

Extract out the logic used by
`AnalyzerFileReference.InMemoryAssemblyLoader` to guess where a given
assembly might be located, and add a couple of unit tests.

Increase Microsoft.DiaSymReader version number so that we can republish ...

MS.VS.Debugger.Engine is now consuming DiaSymReader.

Rebased from https://github.com/tmat/roslyn/tree/DiaSymReader

turn off trigger diagnostic by default as well for unused declaration an...

Harden LocalizableString intrinsically against exceptions

Enable turning a method into an async method or iterator in VB

Enables an edit that updates a regular method to an async method or an iterator in VB. As in C#, there is the restriction in the presence of an active statement in the method body since the debugger doesn't support remapping active statements to a different method (from the original method to the new MoveNext added due to the change to state machine).

Updating the readme to have instructions for CTP 6 and point to these instructions on the wiki instead of creating an ever expanding list. Fixes 1162

Updating the readme to have instructions for CTP 6 and point to these
instructions on the wiki instead of creating an ever expanding list on.

log when VS has hit low memory barrier