[release/3.1] Update dependencies from dotnet/winforms

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/dotnet/winforms

• Build: 20191107.8
• Date Produced: 11/8/2019 5:14 AM
• Commit: 922e41002e66fb10d703705d9be700c8b30cd63d
• Branch: refs/heads/release/3.1
• Updates:
  • Microsoft.Private.Winforms -> 4.8.1-preview1.19557.8

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ Standard Merge Policies Unsuccessful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)
• ❌ Standard Merge Policies There are reviews that have requested changes.

[wtgodbe]

Hold off on merging this until we re-open for GA

[wtgodbe]

Got some failures here from the new Winforms change:

System\Windows\Integration\ElementHost.cs(906,18): error CS1061: 'ElementHost' does not contain a definition for 'ContextMenuChanged' and no accessible extension method 'ContextMenuChanged' accepting a first argument of type 'ElementHost' could be found (are you missing a using directive or an assembly reference?) [F:\workspace_work\1\s\src\Microsoft.DotNet.Wpf\src\WindowsFormsIntegration\WindowsFormsIntegration.csproj]

System\Windows\Integration\ElementHost.cs(987,51): error CS1061: 'ElementHost' does not contain a definition for 'ContextMenu' and no accessible extension method 'ContextMenu' accepting a first argument of type 'ElementHost' could be found (are you missing a using directive or an assembly reference?) [F:\workspace_work\1\s\src\Microsoft.DotNet.Wpf\src\WindowsFormsIntegration\WindowsFormsIntegration.csproj]

@RussKie @vatsan-madhavan who should take a look at these?

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ Standard Merge Policies Unsuccessful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)
• ❌ Standard Merge Policies There are reviews that have requested changes.

[RussKie]

@vatsan-madhavan these failure would be related to dotnet/winforms#2157

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ Standard Merge Policies Unsuccessful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)
• ❌ Standard Merge Policies There are reviews that have requested changes.

[vatsan-madhavan]

This can't be merged as-is.

[vatsan-madhavan]

Ok to merge once build passes

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ Standard Merge Policies No un-ignored checks.
• ❌ Standard Merge Policies There are reviews that have requested changes.

[wtgodbe]

@vatsan-madhavan we can merge this since #2168 is already in, but we probably should've waited to merge both until the branches open for GA. I'll hold everything at core-setup once these get past wpf-int.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ✔️ Standard Merge Policies Succeeded - Successful checks: dotnet-wpf CI, dotnet-wpf CI (Build Windows_NT Build_Release_x64), dotnet-wpf CI (Build Windows_NT Build_Debug_x64), dotnet-wpf CI (Build Windows_NT Build_Release_x86), dotnet-wpf CI (Build Windows_NT Build_Debug_x86)
• ❌ Standard Merge Policies There are reviews that have requested changes.