Restored requirement for struct constructors to always have formal param...

Add imports for extension add methods

Add hoisted catch block exception to the local scope so the local is available to the EE

using SpecializedTasks to avoid allocation.

Use empty array for unspecified public key instead of default(ImmutableArray<byte>) ...

Fixes #1029

While overall parameterless constructors in structs are valid from IL perspective, without a convenient way to declare them they were virtually nonexistent. As we performed more and more testing, we kept discovering cases where parameterless struct constructors caused inconsistent behavior in libraries or even in some versions of CLR.

After reconsidering the potential issues arising from breaking long standing assumptions, we decided it was best for our users to restore the requirement on struct constructors to always have formal parameters.

This reverts commit b37052d0.

This reverts commit 90215346.

This reverts commit b30cf91c.

fix crash due to control following through next statement

Add a CI build script

Make the order of symbols returned from DataFlowAnalysis deterministic

Delete the public TriggerDiagnosticDescriptor type.

And seal its base type DiagnosticDescriptor.

(Fixes #789, #843)

Instances of vbcscompiler.exe may hang around for a few minutes after a
Jenkins run, locking files and causing new runs on the same system to
fail. To address this, we add a script to setup the environment, run the
build and test, and then kill any instances of vbcscompiler.exe that are
left around.

Rename of VB Property Backing Fields

Use empty array for unspecified public key instead of default(ImmutableArray<byte>) to avoid issues with JSON serialization

Updates the ENC closure CDI to distinguish between static and this-only closures

use localized resources in unit tests

Fixes #1025 : Replace '!=' check for comparing symbols in AbstractSpeculationAnalyzer with SymbolsAreCompatible check, which basically uses Equals method for comparison. This was causing two equivalent symbols across semantic model and it's speculative model to be reported as incompatible, causing all simplifications to bail out for ?. expression in VB.

There appears to be a merge issue with the NuGet upgrade change that
caused a build break.  This fixes that.

closes #1077

Use actual value and type for ', results'

[Feedback from PR#1051]

Add typing training scenario for ASP.Net projects.

Corrected the doc comment for CodeBlockAnalysisContext

Diagnostics API changes for registering compilation actions, code block actions, and end actions

Fixes #1025 : Replace '!=' check for comparing symbols in AbstractSpeculationAnalyzer with SymbolsAreCompatible check, which basically uses Equals method for comparison. This was causing two equivalent symbols across semantic model and it's speculative model to be reported as incompatible, causing all simplifications to bail out for ?. expression in VB.