This should return vsCMFunctionSub for Subs and vsCMFunctionFunction for
Functions

VB code model should include Declare Sub and Function

Reduce the amount of work done in the pattern matcher.

Set VSSDKTargetPlatformRegRootSuffix

Previously, the way one used a patter matcher was the following:

    var matcher = new PatternMatcher();
    Loop {
        var result = matcher.MatchPattern(candidate, pattern)
    }

Because of this, each time you called MatchPattern, the matcher would have to deconstruct the
pattern into its relevant components (for example, splitting it on dots and decomposing words out
of it).  Now, this decomposition was cached.  However, that still meant checking the cache on each
call to MatchPattern.  This check involved a lock as well as a dictionary lookup.

The new way to use a pattern matcher is:

    var matcher = new PatternMatcher(pattern);
    Loop {
        var result = matcher.MatchPattern(candidate)
    }

This approach means that we only need to decompose the pattern once.  From then on we can reuse
that decomposition for each value we test against.

There were some issues getting xunit to respect the -notrait option
hence we decided to simplify and use ConditionalFact

This change allows provides the option of running our tests in 64 bit
mode.  Simply invoke BuildAndTest.proj in the following manner:

> msbuild /v:m /m BuildAndTest.proj /p:Test64=true

There are a set of tests today that don't run correctly in 64.  All have
been annotated with the trait

> Require32=true

We need to push on these to get a clean 64 bit run.  But short term this
will at least give us protection against regressions.

fix #413 - fix venus crash

Apply spacing options to Using and Catch

Add skipped test for bug in SyntaxTree.GetChanges() found through investigating https://github.com/dotnet/roslyn/issues/320

Add test for bug in SyntaxTree.GetChanges() found through investigating https://github.com/dotnet/roslyn/issues/320

It turns out that there was a fundamental problem with how parameter
names were handled in VB Code Model. Essentially, the CodeParameter
object was created with the modified identifier of the name. So, it
included the ? or () if they were declared and the type character if it
was declared. This made a bit of a mess when it came time to look of the
underlying node. This should fix several problems (not all reported), so
I went ahead and added several unit tests.

Fix up CA1001Tests and adding the System.Runtime.Analyzers.UnitTests to the CI build.

Put ExpressionEvaluator projects back into "Core", "CSharp", "Setup", "VisualBasic" folders in Roslyn.sln...

Put ExpressionEvaluator projects back into "Core", "CSharp", "Setup", "VisualBasic" folders in Roslyn.sln...

Fix for Issue #225: Remove Unnecessary Cast has different behavior between primary single fix and fix all occurrences

Adjust spans to fix off by one bugs in goto brace extend scenarios. fixes #392.

Progression should properly descend into types for IntelliTrace MVC queries

Fixing up test cases now that AsPublicInterfaceImplementation does the right thing and adds the public modifier. Also making sure to add these unit tests to the CI section of the BuildAndTest.proj file

Expose new dotted-pattern matching capabilities from the Pattern matcher.

Fix for #441: Stop showing empty preview for dialog based refactorings

code cleanup.

This will allow IntelliTrace files generated from MVC projects to navigate properly.

Move native PDB serialization of EditAndContinueMethodDebugInformation t...