This reverts commit c6a1c2c8.

This reverts commit ef1f1a43.

This reverts commit 4c341045.

Make sure CompletionItems have DisplayTexts of differing lengths befo…

Don't deploy VSIX during perf correctness run

Use linked files for shared sources

Update CoreFX to RTM,  CoreCLR to the latest bits, SRM to the latest.

Redirect more of MSBuild

There is a long standing bug in the VS SDK which causes builds to fail on deployment errors.  There are no actual deployment issues, the deployment step itself simply fails.  This hits the perf correctness suite pretty regularly and adds no value.  Disabling.

We attempt to bind lambda args against every applicable delegate
type that could be a matching parameter, and then select the
"best" for error recovery.
This also has the effect of removing unbound lambdas from the
bound trees, replacing them with the "best" binding for error
recovery. This makes the semantic model insensitive to any further
trial bindings (i.e. mutation of the unbound lambda cache).
Fixes #12063, #11979, #11901

Remove vestigal "extensionMethodsOfSameViabilityAreAvailable"
thereby reducing coupling between internal compiler APIs.
See also #7740 #5128, where the vestigal APIs were introduced.

Our test utilities had a number of files that were duplicated in test utility projects.  Changed them to be linked files so we didn't have duplicate sources.

Tie language features to the langver flag

Properly implement type inference for C# member access expressions.

Only compute entry points when compiling everything.

Don't invoke SignFiles if there's no files to sign

Fixes #12113

This silences a build warning.

Merge future-stabilization into master

Make sure CompletionItems have DisplayTexts of differing lengths before determining if one is a prefix of the other.

* Test ExportedType table content

* Refactoring of code emitting exported types

* Remove MetadataWriter.GetExportedTypeFlags