Analysis of any code within a local function with IOperation analyzers will produce false or missing diagnostics, as the operation tree doesn't contain any operation nodes within the BoundLocalFunctionStatement. This can be a dogfood blocker for IOperation analyzers on real world code - we had few false reports due this on the Roslyn repo as we use this new language feature, and corresponding rules had to be disabled in the repo.

Update System.Compression.Zip version to prevent downgrade warnings

Only run OOP features if A/B experiment is enabled.

Optimize is null

This reverts commit 6dd74528.

Fixes package downgrade warnings in roslyn-internal

Add a specific WorkspaceKind for test workspaces.

Simplify metadata reference searching in Add-Import.

Remove unused parameter.

Boost priority of NavigateTo when running in OOP server.

Properly use ?. in an expression containing a nullable type.

Skip hanging test TestTagsChangedForEntireFile

Disable flakey test.

Move the symbol mapping service down to the Features layer.

Don't allow properties for a DocumentSpan to be null.

Moving FindUsages data type down to Features layer.

Properly pass cancellation token along when spawning task.

Emit tuple names on property setter parameters

Check for bad dynamic arguments to local function

Ensure that IOperations nodes within an IsPatternExpression are part …

Fix crash with using 'replce property with method' with interfaces in VB

Fix EditAndContinueDiagnosticUpdateSource.ReportDiagnostics to return correct set of documents (#19786)