Related to #23483

We stop calling string.GetHashCode() at compile time and placing the value in the
generated code because that is not deterministic. Instead we use FNV1a hash code.

For VB, which does not have this bug, we update the implementation to use a more
reliable case-mapping method (see #2116)
Fixes #23020

Remove * from CODEOWNERS file

Remove the uber VSIX

These projects are no longer needed. Removing them.

Historically these were used to create an uber VSIX that nested all of
our other VSIX for a single deployment point. In practice though we have
not actually used these. The install / uninstall issues around them are
too problematic.

Should the uninstall issues be fixed we will consider bringing these
back

Make C# and VB CommandLineParser.Script public

Enable concurrent execution for all built-in C# analyzers

Do not publish in tests.sh

Avoid IEnumerable allocations when flusing data to sqlite.

Reduce Location allocations while running analyzers.

Turns out the * only means the files in that immediate directory
counts as being matched. That's not what we intended.

* Variable misuse ML model found a bug where wrong variable is used to call a method.

* more variable misusage cases

Publish NuGet packages for 15.6

Use binary log in microbuild

The imported build tasks targets sets a nonexistent default target

This enables the generation of binary logs for our build when running in Microbuild.
Having the logs available helps in post-build debugging of errors. We tend to get a
number of microbuild only failures that are impossible to track down without logging
like this.

Once this is merged i will be adding a task to our VSTS build definition to publish
these post build.

Unify the source of compiler toolset files

This check existed to verify that the two lists of compiler files was
kept in sync. Now that there is only one list there is no reason to run
the check anymore.

Remove unused tool ProcessWatchDog

This change makes our existing internal API for parsing script command-line arguments public for the community to use with custom script runners. In addition, the API has been renamed from `ScriptRunner` to `Script`, since it should be clear to consumers since the API is prefixed by the CommandLineParser class (i.e. `CSharpCommandLineParser.Script` or `VisualBasicCommandLineParser.Script`).

Use TargetFrameworks

It's gross, but we need to publish *something* until ILAsm is exposed as
a normal assembly

Update feed tasks version

Emabarrasing typo from a previous PR

This removes the last usages of the CompilerFiles hard coded list of
files in favor of the version read from the toolset nuspec. This reduces
the number of places that need to be kept in sync when we make changes.

This changes the file set used to build the VS toolset to match that of
the standard compiler toolset. Simply re-use the file list in the
compiler nuspec file here.

This actuall found a bug in our current implementation. We were not
copying the config file for csi.exe in the VS toolset.

All of the XML literals in the file use the same xmlns value. Set a
global import so we can simplify the building of the literals.