- Extract a local
- Remove unnecessary type argument
- Fix up expected/actual in Assert

Fallback matching for manifest "AssemblyFiles"...

In some scenarios, it appears that the strings for AssemblyFiles contain file extensions (.dll, etc).  However, the module names in the "modulesByName" (ModuleMetadata.Name) will not.  To work around this, implement a "fallback" match that removes the possible file extension.

Update Code Model to support ReadOnly and WriteOnly VB auto-properties

Disable a few unit tests

These are failing in certain build configurations.

Made use of extension Add methods in Expression lambdas a compiler error...

Dont Assume Certain Node Are Always Parented

Fix 1118 : Dont assume that some of the nodes are always parented.
Always check if the parent is not null before accessing the parent.

Dont disturb whitespace preceding comments

When validating references, ignore duplicates

Expression Trees specifically require that element initializer methods are instance methods.
Fixes #310

Fix a NRE in VB query expression binding

Fixes #1099

There were uses of private fields in #if blocks that needed to be
adjusted to the renamed fields.

Detect and report attempt to use abstract event through base

Introduce a new AbstractEncProject for CSharpProject and VisualBasicProject to extend.

Enable editing methods with anonymous types and remove unused rude edit kinds

This fixes up the misaligned comments that came from the formatting bug
described in #1177.

closes #1140

This is the initial run of the code formatter on the VB compiler source code.  Further runs I'll expand on this to include all VB code in a future run.

New EvaluationContext cache-invalidation strategy

Remove UseTabOnlyForIndentation since this is a public option & there
are no testcases for this option. With the changes the option is no
longer used making it obsolete. Fix the broken testcase which was
asserting the undesired behavior

Cleaned up C++ project targets

VB 14 supports ReadOnly and WriteOnly auto-properties. Code Model's
CodeProperty2.ReadWrite should return the correct value for them.

Ignoring references, which are obviously the high-order bit, the old
strategy was to confirm that the methodToken, methodVersion, and smallest
containing scope were the same as the current context.  This had two
problems:

1) C# hoisted locals are not reflected in scopes and so we were not
invalidating the cache when we stepped across scope boundaries in async
and iterator methods.

2) We had to access the PDB in order to check whether the cache was still
valid (to figure out the smallest containing scope).

We propose a new approach: compute the largest span around the current IL
offset in which there are no scope boundaries (including hoisted local
scopes).  Then, when check cache validity by doing a simple span
containment check (plus methodToken and methodVersion, obviously).

Downside 1: We need all scopes in the method, not just the containing
ones.

Downside 2: If you somehow step around a nested scope (e.g. using
breakpoints), the new approach will invalidate the cache, whereas the old
one did not.

Check SyntaxNodeOrToken is a SyntaxNode before converting

This project does the appropriate Enc hookup, and implements the interfaces that the debugger
QIs for to do Enc interaction.

For C# and VB, nothing will change.  For TypeScript, we will continue subclassing AbstractProject.
By doing this, we will not interact with the Enc system at all.  This will help avoid undesirable
behavior (like having our files become read-only when entering debugging).

It seems that VsProject's references may include duplicate versions of
mscorlib for portable projects, so remove duplicates before comparing
against our workspace set of references.

This fixes #1083.

Fix Extract Method and Generate Variables in Conditional Access Expressions.

Fixes #751.

Properly handle ConditionalAccessExpressions in ExpressionSyntaxExtensions::CanReplaceWithLValue. When conditional access expressions begin with some form of member binding expression (starts with the dot operator), they cannot be replaced with an LValue. @jmarolf contributed commit cf3dd545

This issue does not affect VB as VB language parses this differently than C#.

Fix internal TFS bug 1130555 : Getting Parent of SyntaxNodeOrToken
does not need conversion to Node or Token.

When converting a SyntaxNodeOrToken to a Node or Token use IsNode or IsToken.

In this particular instance, we have introduced the check in
InlIneTemporaryCodeRefactoringProvider to prevent crash. We will still
have to find the scenario that triggered this situation.