[master] Update dependencies from dotnet/runtime

[dotnet-maestro]

This pull request updates the following dependencies

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

• Build: 20200104.2
• Date Produced: 1/5/2020 3:15 AM
• Commit: b174fdce50303f7aad53022ae623b5a9629289b1
• Branch: refs/heads/master
• Updates:
  • Microsoft.NETCore.App -> 5.0.0-alpha.1.20054.2

Coherency Updates

The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format

• Microsoft.NETCore.Platforms -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• Microsoft.Win32.Registry -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• Microsoft.Win32.SystemEvents -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.CodeDom -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.Configuration.ConfigurationManager -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.Drawing.Common -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.Resources.Extensions -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.Security.Cryptography.Cng -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.Security.Permissions -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• System.Windows.Extensions -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• Microsoft.NET.Sdk.IL -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)
• Microsoft.NETCore.ILAsm -> 5.0.0-alpha.1.20054.2 (parent: Microsoft.NETCore.App)

Microsoft Reviewers: Open in CodeFlow

[ghost]

Go, you big red fire engine!

[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.

[safern]

@dagood @mmitche should we also remove the CoherentParentDependency from this file?

[dagood]

It's not necessary anymore and should be removed, but darc seems to have handled it ok in this PR. (It updated to the one we published, not the one that dotnet/runtime's Version.Details.xml depends on.) I'm a little surprised it handled it ok, but if it works, it works.

[RussKie]

The PR is failing... Any ideas?

[dagood]

The official build doesn't publish to dotnetcli yet, more info at dotnet/runtime#98 (comment). Thought I commented about it here, but looks like I didn't, sorry.

[RussKie]

@vatsan-madhavan would it cause problems for you if we merge this?

[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.

[dagood]

I don't expect the CI failures to be fixed yet (and I'd expect them to cause issues locally as well). I do have a PR in progress to get the dotnetcli publish going through: dotnet/runtime#1092.

[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.

[dagood]

I'd recommend closing this so a new PR can be generated without conflicts. (I don't have permissions.)

You may also want to add some unchanging lines between some of the global.json lines to avoid conflicts between auto-update PRs in the future. (That's what https://github.com/dotnet/runtime/blob/f5ba13fb4416519c21a468f544499ad75f704dae/global.json#L19 is for.)

[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.

[RussKie]

You may also want to add some unchanging lines between some of the global.json lines to avoid conflicts between auto-update PRs in the future. (That's what dotnet/runtime:global.json@f5ba13f#L19 is for.)

Nice hack 💯

[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-winforms CI, dotnet-winforms CI (Build Windows Release), dotnet-winforms CI (Build Windows Debug)
• ❌ Standard Merge Policies There are reviews that have requested changes.

[RussKie]

@dagood the PR is still failing to build due to an unresolved dependency

##[error]src\Accessibility\src\Accessibility.ilproj(0,0): error NU1102: Unable to find package runtime.win-x64.microsoft.netcore.ilasm with version (>= 5.0.0)
  - Found 1178 version(s) in dotnet-core [ Nearest version: 5.0.0-alpha.1.20054.2 ]
  - Found 792 version(s) in dotnet-coreclr [ Nearest version: 5.0.0-alpha1.19564.1 ]
  - Found 9 version(s) in nuget.org [ Nearest version: 2.0.8 ]
  - Found 0 version(s) in arcade
  - Found 0 version(s) in dotnet-eng

[dagood]

@RussKie That's bizarre that it's looking for 5.0.0 rather than the actual version, I can't explain that. Can you file an issue in dotnet/runtime with some more env info so the authors of that package can investigate?

[dagood]

I can repro with .\build.cmd on win10 with PR #2638, I'll file an issue unless you beat me to it.