[main] Update dependencies from dotnet/windowsdesktop

[dotnet-maestro]

This pull request updates the following dependencies

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

• Coherency Updates:
  • Microsoft.NET.Sdk.WindowsDesktop: from 9.0.0-alpha.1.23512.1 to 9.0.0-alpha.1.23519.4 (parent: Microsoft.WindowsDesktop.App.Ref)

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

• Subscription: 43b77b68-0b3c-49dd-3915-08d8e9750bf8
• Build: 20231019.18
• Date Produced: October 20, 2023 3:10:30 AM UTC
• Commit: 557ec081e6ca0fb7f8deb21f87582242c5f08af8
• Branch: refs/heads/main

• Updates:
  • Microsoft.WindowsDesktop.App.Ref: from 9.0.0-alpha.1.23513.1 to 9.0.0-alpha.1.23519.18
  • Microsoft.WindowsDesktop.App.Runtime.win-x64: from 9.0.0-alpha.1.23513.1 to 9.0.0-alpha.1.23519.18
  • VS.Redist.Common.WindowsDesktop.SharedFramework.x64.9.0: from 9.0.0-alpha.1.23513.1 to 9.0.0-alpha.1.23519.18
  • VS.Redist.Common.WindowsDesktop.TargetingPack.x64.9.0: from 9.0.0-alpha.1.23513.1 to 9.0.0-alpha.1.23519.18
  • Microsoft.NET.Sdk.WindowsDesktop: from 9.0.0-alpha.1.23512.1 to 9.0.0-alpha.1.23519.4

[dotnet-maestro]

Notification for subscribed users from https://github.com/dotnet/windowsdesktop:

@dotnet/wpf-developers

Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.

• This pull request contains changes from your source repo (https://github.com/dotnet/windowsdesktop) and seems to have failed checks in this PR. Please take a peek at the failures and comment if they seem relevant to your changes.
• If you're being tagged in this comment it is due to an entry in the related Maestro Subscription of the Build Asset Registry. If you feel this entry has added your GitHub login or your GitHub team in error, please update the subscription to reflect this.
• For more details, please read the Arcade Darc documentation

[dotnet-maestro]

Notification for subscribed users from https://github.com/dotnet/windowsdesktop:

@dotnet/wpf-developers

Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.

• This pull request contains changes from your source repo (https://github.com/dotnet/windowsdesktop) and seems to have failed checks in this PR. Please take a peek at the failures and comment if they seem relevant to your changes.
• If you're being tagged in this comment it is due to an entry in the related Maestro Subscription of the Build Asset Registry. If you feel this entry has added your GitHub login or your GitHub team in error, please update the subscription to reflect this.
• For more details, please read the Arcade Darc documentation

[dotnet-maestro]

Notification for subscribed users from https://github.com/dotnet/windowsdesktop:

@dotnet/wpf-developers

Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.

• This pull request contains changes from your source repo (https://github.com/dotnet/windowsdesktop) and seems to have failed checks in this PR. Please take a peek at the failures and comment if they seem relevant to your changes.
• If you're being tagged in this comment it is due to an entry in the related Maestro Subscription of the Build Asset Registry. If you feel this entry has added your GitHub login or your GitHub team in error, please update the subscription to reflect this.
• For more details, please read the Arcade Darc documentation

[dotnet-maestro]

Notification for subscribed users from https://github.com/dotnet/windowsdesktop:

@dotnet/wpf-developers

Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.

• This pull request contains changes from your source repo (https://github.com/dotnet/windowsdesktop) and seems to have failed checks in this PR. Please take a peek at the failures and comment if they seem relevant to your changes.
• If you're being tagged in this comment it is due to an entry in the related Maestro Subscription of the Build Asset Registry. If you feel this entry has added your GitHub login or your GitHub team in error, please update the subscription to reflect this.
• For more details, please read the Arcade Darc documentation

[v-wuzhai]

@dotnet/dotnet-windowsdesktop-admin Could you take a look at the failures here?

[dreddy-work]

infra issue : ShellJSInternalError: ENOSPC: no space left on device, write Rerunning.

[dreddy-work]

WPF tests failed @singhashish-wpf / @lonitra

[dreddy-work]

Tests getting wrong SDK version. @ViktorHofer / @mmitche any idea where 9.0.100-ci version of sdk coming from?

C:\h\w\9F9E08EB\p\d\sdk\9.0.100-ci\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\Microsoft.WinFX.targets(211,9): error MSB4062: The "Microsoft.Build.Tasks.Windows.MarkupCompilePass1" task could not be loaded from the assembly C:\h\w\9F9E08EB\p\d\sdk\9.0.100-ci\Sdks\Microsoft.NET.Sdk.WindowsDesktop\tools\net8.0\PresentationBuildTasks.dll. Could not load file or assembly 'C:\h\w\9F9E08EB\p\d\sdk\9.0.100-ci\Sdks\Microsoft.NET.Sdk.WindowsDesktop\tools\net8.0\PresentationBuildTasks.dll'. The system cannot find the path specified.

should these be updated by arcade? https://github.com/search?q=repo%3Adotnet%2Fwindowsdesktop+net8.0&type=code

@lonitra

[ViktorHofer]

AFAIK the 9.0.0-ci SDK is the live built one in the sdk repository. That's the expected one.

Regarding the PresentationBuildTasks.dll error, I see that we already talked about this one year ago: #28897. Maybe that helps? Sounds like the consensus last year was that wpf needs to build with a newer SDK?

should these be updated by arcade?

I believe that we need to wait for msbuild to target net9.0 before we can update the first two hits. NetMinimum is supposed to point to net8.0 as that's the minimum supported .NETCoreApp TFM when .NET 9 ships.

[ViktorHofer]

Reason for the failure is dotnet/wpf@69985c9#r130418367

[singhashish-wpf]

Pushed the suggested change. Thanks @ViktorHofer @dreddy-work