Update cibuild.cmd to call a different script

vcvarsall.bat will call vcvars32.bat, which uses some environment variables that are not defined. Instead call vsdevcmd.bat, which *also* uses these environment variable, but we've already patched up these files on our build systems to work around the issue.

This fix was cherry-picked from 1814e27a (made against the stabilization branch.

vcvarsall.bat will call vcvars32.bat, which uses some environment
variables that are not defined. Instead call vsdevcmd.bat, which
*also* uses these environment variable, but we've already patched
up these files on our build systems to work around the issue.

No exceptions for missing rule set includes

**Bug:** Fixes DevDiv bug 1184500

**Customer Scenario**
Customer has an existing solution that uses FxCop, and uses a custom rule set that includes one of the "built in" FxCop rule sets, such as MinimumRecommendedRules.ruleset. When building this solution with Roslyn compilers, his build will fail with errors about MinimumRecommendedRules.ruleset not being found.

**Fix Description**
The issue is that the Roslyn compilers use the same rule set files as FxCop, but do not have all the same logic for resolving included files. They can find included rule sets at absolute paths, and at paths relative to the parent rule set, but they do not know about the extra directories FxCop checks after that. The fix here is to simply ignore any included rule set files that cannot be found.

We've made this fix before, actually, but it was lost in the code shuffle of commit 7e277f66.

**Testing done**
We had an existing unit test covering this scenario, but it was skipped. I updated the test and un-skipped it. I validated that it failed without my fix, and passed with the fix.

Update cibuild.cmd to call a different script

vcvarsall.bat will call vcvars32.bat, which uses some environment variables that are not defined for the baseline build of VS we're currently using. Instead call vsdevcmd.bat, which *also* uses this same environment variable, but we've already patched it up on our build systems to work around the issue.

Fix typos

EE: "Internal Error evaluating expression" when instruction does not map to IL offset

Port  dd46a88a  to stabilization.

This reverts commit 2037411c.

vcvarsall.bat will call vcvars32.bat, which uses some environment
variables that are not defined. Instead call vsdevcmd.bat, which
*also* uses these environment variable, but we've already patched
up these files on our build systems to work around the issue.

Rename should kick out in bad syntax

Bail on rename session when entering debug run mode

Remove extra files from VSIXes

Conflicts:
	src/ExpressionEvaluator/CSharp/Test/ExpressionCompiler/ExpressionCompilerTests.cs
	src/ExpressionEvaluator/VisualBasic/Test/ExpressionCompiler/ExpressionCompilerTests.vb

Mechanically apply <Private>False</Private> to the newly-appeared
references.

EE: "Internal Error evaluating expression" when instruction does not map to IL offset

port interactive fixes to stabilization

Fix spelling of public API parameters

make sure we lock before changing shared state.

Propagate CharSet for structs implementing fixed buffers from the field's containing type.

Move Cross Platform document to source code control

Update NuGet package creation to put NuGets in a single folder, rather than Shipping/NonShipping.

This moves the cross platform instructions to a file checked into
source code control.  This process naturally envolves with our
code and hence should live next to it.

Bonus: External customers can send PRs to fix the many typos and
errors that I keep introducing.

Conflicts:
	src/Workspaces/Core/Portable/PublicAPI.txt

[Automated] Merge 'stabilization' into 'master'

Fixes #3392.

add timeout on implicit cache

made our implicit compilation cache to have a timeout. if nobody uses cached compilation for 10 seconds, it will be dropped from the cache.

also, made MRU cache to properly mark most recently used compilation.

...rather than looping infinitely.  This parallels the C# behavior.

Fixes #3316.

related to #2909
Closes #3056

the ordering guarantees (deterministic, and for same kind they appear in input order).

Fixes #2909

The Roslyn compilers use the same rule set files as FxCop, but do not
have all the same logic for resolving included files. They can find
included rule sets at absolute paths, and at paths relative to the
parent rule set, but they do not know about the extra directories FxCop
checks after that. Currently they raise an error if an included rule set
is not found, but we want them to simply ignore and continue.

We've made this fix before, actually, but it was lost in the code
shuffle of commit 7e277f66.

Fixes DevDiv bug 1184500.

Add the ability to dump EnC delta PDB to pdb2xml tool