Improve undo stack titles for suggestions applied via light bulb

Use assembly name for analyzer ID

Use the actual assembly name for `AnalyzerFileReference.Id`, instead of
a lowercase version of the file name.

There are places we are currently using `AnalyzerReference.Id` when what
we may want is `AnalyzerReference.DisplayName`. Notably, in the rule set
editor. This means that after my recent change to simply return the
lowercase version of the analyzer assembly's file name, the rule set
editor started showing "microsoft.codeanalysis.analyzers.dll" instead of
"Microsoft.CodeAnalysis.Analyzers".

The "right" solution would probably involve an API to map from an ID
back to an `AnalyzerReference`, and then using the `DisplayName` in the
rule set editor instead of the `Id`. At this stage in the release cycle,
however, I'm going with a simpler solution: make `AnalyzerFileReference`
return the same value for `Id` and `DisplayName`, and get that value by
reading the assembly name from the file itself, like we used to.

Fixes #2781 and #2782.

Fix typos

Fix analyzer type load error reporting, API

Visit InitialValue as rvalue in AbstractFlowPass(Of ).VisitFieldOrPropertyInitializer.

Exception)...

Fix typos

Change pipe checksum to SHA256

Implement Dynamic View expansion...

(fixes #1743)

Use the actual `AssemblyIdentity` for `AnalyzerFileReference.Id`, instead of
a lowercase version of the file name. Also use `AssemblyIdentity.Name` as the
`DisplayName`.

If we can't read the file for whatever reason, fall back to strings
generated from the file path.

Fixes #2781 and #2782.

Fix nulls in AnalyzerDependencyChecker.

Currently we use a `Task.FromResult(null)` as a sentinel task before a
real dependency check has been queued up. This works fine until we try
to access the results of this task, and things blow up.

Instead, we should create an AnalyzerDependecyResults.Empty singleton,
and create a task from that.

Also, this change catches all exceptions coming out of
`AnalyzerDependencyChecker`, to avoid bringing down VS.

Disable Deterministic PDB GUID generation for RTM

Fixes #2896.

Only return a fix if the assembly identity matches the diagnostic mes…

Don't leak Workspace objects from AnalyzerAndOptions

Add tests for #976. The actual fix for this was in the compiler #2540.

Introduce local on interpolated string expressions should not generate a
constant, but a variable.

Add tests for #976. The actual fix for this was in the compiler #2540.

Introduce local on interpolated string expressions should not generate a
constant, but a variable.

Guard visitors against stack overflow exceptions

Currently we use a `Task.FromResult(null)` as a sentinel task before a
real dependency check has been queued up. This works fine until we try
to access the results of this task, and things blow up.

Instead, we should create an AnalyzerDependecyResults.Empty singleton,
and create a task from that.

Also, this change catches all exceptions coming out of
`AnalyzerDependencyChecker`, to avoid bringing down VS.

Handle BoundSequence as an assignment target in CodeGenerator.EmitAssignmentExpression.

Dont offer cast simplification fixes for explicit reference conversions

For code snippets such as below: "Base M(Base b) => (Derived)b;", we currently offer cast removal for cast to derived. However, this involves an explicit/narrowing conversion and hence can lead to an exception or data loss. The only way to detect such redundant casts is via flow analysis, which is not currently in our scope.

Fix is to bail out early for such cast expressions. I have also fixed incorrect tests that were added to ensure the current behavior.

Fixes #2761 

Improve the documentation comments on CodeFixContext constructors and CodeFixProvider.RegisterCodeFixesAsync methods.

Fixes #2643 

Improve the documentation comments on CodeFixContext constructors and CodeFixProvider.RegisterCodeFixesAsync methods.

Fix breakpoint handling and EnC of queries containing Select and GroupBy clauses that don't translate their select/group-by expression to lambda

Add regression tests for #2441

Fixes #2878.

For code snippets such as below: "Base M(Base b) => (Derived)b;", we currently offer cast removal for cast to derived. However, this involves an explicit/narrowing conversion and hence can lead to an exception or data loss. The only way to detect such redundant casts is via flow analysis, which is not currently in our scope.

Fix is to bail out early for such cast expressions. I have also fixed incorrect tests that were added to ensure the current behavior.

Fixes #2761

Make ICompilationFactoryService internal

After discussing the matter, @agocke, @tmat and I have concluded that the
implementation in EETypeNameDecoder will never be affected by the bug the
compiler was seeing.  However, we still felt it would be worthwhile to
make the implementations consistent.  There is, however, no test, since
the behavior is unchanged.

I added some using/import tests since they use the compiler implementation
(which has already been fixed).

Fixes #2441