- Remove invoke mono script
 - Pass through debug flag via supported arcade mechanism instead

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19326.2

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19324.24

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19323.4

* Update dependencies from https://github.com/dotnet/arcade build 20190620.1

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19320.1

* Bring changes from https://github.com/dotnet/arcade/pull/3076

* Update dependencies from https://github.com/dotnet/arcade build 20190621.75

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19321.75

* Update dependencies from https://github.com/dotnet/arcade build 20190622.2

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19322.2

1. Make IDE0069 (DisposableFieldsShouldBeDisposed) conservative by bailing out on disposable types that don't have the Dispose implementation, but rely on base type implementing it and having virtual helper methods for dispose functionality

2. Make IDE0067 (DisposeObjectsBeforeLosingScope) conservative by bailing out on disposable objects that are passed as arguments to methods in metadata.

Requires updating to a new FlowAnalysisUtilities version.
Fixes #36498

Fixes #36037

(cherry picked from commit 0a39cf90)

* Update publish data for 16.2-preview3 snap

* Update PublishData.json

A build error is also reported for the lack of an appropriate constructor.

* mark NFW from OOP critical

currently, whenever OOP throws an exception, we show infobar saying "restart VS". whenever that happens, we report NFW. now those NFW will be marked as critical and we will stop reporting NFW after that in VS.

basically making critical NFW behavior same as fatal watson in VS. and management will treat critical NFW same as fatal watson.

also, now we will show callstack like code fix exception when info bar is shown

* xml document fix

* fix build break.

* changed button to hyper-link to follow same pattern as other info bar (code fix)

show remote exception in callstack view.

* introduced enum for Watson Severity

* Update ILAsm and ILDasm version to match expected SDK version

* Fixed version numbers

* Add InteractiveHost as a NuGet package

* Make InteractiveWindow a package dependency

* Update InteractiveWindow version to 2.8.0

* Add missing package dependencies

See dotnet/roslyn-analyzers#2498

Specify the version number in pieces so we can generate the assembly version using just the major and minor version numbers.

Improves the workaround for Microsoft/MSBuildLocator#16

Additionally, we do not mark the package reference to in Features.csproj as PrivateAsset as this leads to the assembly not getting included in the Features NuGet package and causes Omnisharp's analyzer execution to throw missing dependency assembly load errors.
Also update ExpectedDependency in DevDivInsertionFiles.csproj

Additionally, we do not mark the package reference to in Features.csproj as PrivateAsset as this leads to the assembly not getting included in the Features NuGet package and causes Omnisharp's analyzer execution to throw missing dependency assembly load errors.
Also update ExpectedDependency in DevDivInsertionFiles.csproj

Address PR feedback: remove static cache, make FlowAnalysis utilities assembly load lazy and revert reference add to the FlowAnalysis assembly in Workspaces (only referenced in Features now).

(DisposableFieldsShouldBeDisposed)

We will now flag disposable creations in methods that do not escape the
method body (return value, out/ref params, assign to field/property, add
to collection, etc.). Additionally, we also flag disposable fields of
disposable types that are not disposed in the type's Dispose method.
Ported analyzers share the core dataflow analysis computation with the
analyzers in the roslyn-analyzers repo
(Microsoft.CodeAnalysis.FlowAnalysis.Utilities). This PR does not add
any code fixes. We already have a code
refactoring that offers wrapping a disposable creation within a using
statement. I am hoping to extend that to handle more cases and also
possibly convert it to a code fix in follow-up PR(s).