The problem arises when more than one expansion shares the same value -
for example, those parented by a common AggregateExpansion.  Since this is
an optimization anyway (the debugger would eventually close them on its
own), we'll just conservatively focus on data items without children.

Fixes #901.

Fix couple of issues in CSharpDeclarationComputer (issue #592): 

1.Add declaration info for ArrowExpressionClauseSyntax: For properties and indexers, this node declares the getter method symbol whose IsImplicitlyDeclared flag is false and hence the analyzer symbol actions need to be invoked for this getter.

2.Previously executable code block actions for nodes within ArrowExpressionClauseSyntax were executed with parenting property symbol as the owning symbol. This change fixes it to have the declared getter method symbol as the owner of executable block for ArrowExpressionClauseSyntax.

I have added IDE and compiler driver tests for symbol analyzer, syntax node analyzer and executable code block analyzer for expression bodied members.

Fix #409. Add explicit StringComparison.Ordinal where it was intended.

Hierarchical Find References

Add stack guards for the ParseExpression and ParseStatement calls.
These are other public entry points into the parser which needed to be
guarded in the same way as ParseSyntaxTree.

close #839
close #848

The MSBuild workspace code should respect the ReferenceOutputAssembly
flag.  Before only the C# implementation of MSBuild was doing so.  Now
all implementations will properly respect the flag.

closes #900
closes #909

Show 'else' within Ifs within Elses

Fixes #719 

Show expression completion within casts

Fixes #717 

Automatic brace completion of "(" parses as a cast, but the user might
be trying to type a parenthesized expression.

Don't leak exceptions from AssemblyResolve handler

In this initial implementation, find references results are now grouped by the definition that they directly reference.

For symbols defined in metadata, we previously showed the references without showing the definition itself. We now show the metadata definition as well.

1. Add declaration info for ArrowExpressionClauseSyntax: For properties and indexers, this node declares the getter method symbol whose IsImplicitlyDeclared flag is false and hence the analyzer symbol actions need to be invokedfor this getter.

2. Previously executable code block actions for nodes within ArrowExpressionClauseSyntax were executed with parenting property symbol as the owning symbol. This change fixes it to have the declared getter method symbol as the owner of executable block for ArrowExpressionClauseSyntax.

Fix broken VB EC tests.

Add support for accessors and WriteOnly to SyntaxGenerator

Move serialization specific BitArray helpers to where they are used

fix resource string that was causing an invalid xml doc comment to be generated

Add a comment explaining why
`AnalyzerFileReference.InMemoryAssemblyLoader.CurrentDomain_AssemblyResolve`
catches all exceptions.

Make locals case-insensitive in the VB EE

fix a case where we subscribe to an event while global operation is alre...

update unit tests to use localized resources

1) Pass StringComparer.OrdinalIgnoreCase to the dictionary of (real)
locals.
2) Canonicalize (i.e. lowercase) the names of pseudo-variables and
locals declared in the Immediate window (because the debugger APIs
we call are case-sensitive).

one of test found a case where we subscribe to an event while global operation is running. and we crash when stop event is fired.

DkmClrValue.GetMemberValue also needs a DkmInspectionContext parameter...

EE: Bind to intrinsic methods from assembly supplied by the debugger

These files are a hold over from when Roslyn was in TFS.  They aren't
needed anymore now that we are in git.

closes #858

Fix for #271: Compiler crashes if it cannot locate resources for analyzer

CLR calls us back to search for presence of satellite resource assembly with ".resources" suffix, before attempting to go back to the main assembly as a fallback for resources. However, during this callback we were trying to load the satellite assembly without checking if the file exists on disk, causing an unhandled FileIOException.

Adding the NeutralResourcesLanguageAttribute in PR #831 caused the CLR to directly go to the Main assembly for resources, without making the satellite assembly callback.

I removed this attribute locally from our analyzer assemblies, and with the added File.Exists check, we correctly return null for satellite assembly callbacks and CLR eventually falls back to the Main assembly for resources and we are able to find resources.