The CLI toolchain only supports string literals inside of a RESX file.
Other blobs, such as a reference to a file on disk, are not supported.
Instead their value gets embedded directly as a string literal (type is
ignored). Only supported mechanism is to embed them as a manifest
resource stream.

https://github.com/Microsoft/msbuild/issues/2221

Enable VB emit tests on CoreClr

* Update branches for target-typed-new and caller-expression

* Add "pattern-based using"

Bind goto case expression even in presence of errors

Assert that IArrayInitializationOperation.Type is always null in test visitors

* Change goldbar text for updating keyboard bindings

* Fix text placeholder

* Update text

Fixes #8891

* Move VS specific targets to VisualStudio.targets

* Move optimization targets to RepoToolset/OptimizationData.targets

* Move SourceLink targets to RepositoryInfo.targets

* Remove workarounds for fixed issues

* Move workrounds to Workarounds.targets

* Clean up binding redirect generation properties

* Remove unused targets

* Normalize PushToBlobFeed parameters to values used by RepoToolset.

Add ControlFlowGraph.Create overload that takes syntax and semantic m…

Infrastructure misc changes

The CLI toolchain only supports string literals inside of a RESX file.
Other blobs, such as a reference to a file on disk, are not supported.
Instead their value gets embedded directly as a string literal (type is
ignored). Only supported mechanism is to embed them as a manifest
resource stream.

https://github.com/Microsoft/msbuild/issues/2221

The CLI toolchain only supports string literals inside of a RESX file.
Other blobs, such as a reference to a file on disk, are not supported.
Instead their value gets embedded directly as a string literal (type is
ignored). Only supported mechanism is to embed them as a manifest
resource stream.

https://github.com/Microsoft/msbuild/issues/2221

Create Control Flow Graph regions to designate life-time of flow captures in a Control Flow Graph. A region should start as soon as a capture is needed to accurately represent the order of evaluation within operations involving control of flow. However, it should not start too soon. For example, if there is a branch that represents an execution path that bypasses the use of a capture completely, that branch should not be included into the region for the capture. Also, the region should end as soon as the last operation referencing the capture is reached.

Added 15.8-preview3 builds to README

* Use System.Runtime.Loader light-up package

Expose IOperation.SemanticModel

Fixes #18225

bug fix: don't optimize interpolations when in an expression lambda

Remove testoperationvisitor workaround now that bug is fixed.

Skip 3 failing NetCoreTests until fixed

Unskip test for fixed IOperation issue

Move to new MSBuild drop

Original issue: https://github.com/dotnet/roslyn/issues/23821

Correct doc about Equivalence Key

Test alias to forwarded type