-
Notifications
You must be signed in to change notification settings - Fork 982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.Private.Windows.Core is not included in the runtime pack #11282
Comments
@Olina-Zhang can your team confirm this please? |
I didn't reproduce the problem with the .Net 9.0 Preview3 build machine at hand. |
Maybe it happens on the nightly build only? |
Tried to repro and got same results as above. Could not repro issue with .NET 9 preview 3 and could not verify with nightly build. I suspect that we do not publish nuget package for unreleased previews which is why the errors are produced. We had previously had an issue similar to this when we first introduced System.Private.Windows.Core, where the assembly was not present and needed to be, but this had since been fixed via dotnet/windowsdesktop#4084. Looked through the history there and it doesn't seem that we had regressed this behavior. @hez2010 to clarify, had you experienced this issue on .NET 9 Preview 3, nightly build, or both? |
It's reproducing on the nightly build. <configuration>
<packageSources>
<add key="dotnet9" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json" />
</packageSources>
</configuration> I'm using 9.0.100-preview.5.24230.22. |
Fixed via dotnet/windowsdesktop#4366 in main and dotnet/windowsdesktop#4369 in preview 4 |
Verified the issue on 9.0.100-preview.5.24304.3 Test Pass build, the issue has been fixed that have the same results as above. |
.NET version
.NET 9 nightly
Did it work in .NET Framework?
Yes
Did it work in any of the earlier releases of .NET Core or .NET 5+?
No response
Issue description
System.Private.Windows.Core.dll
is not included in the runtime pack, and leading to the below exception while running a self-contained published app.Steps to reproduce
The text was updated successfully, but these errors were encountered: