-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
UWP app consuming 1.1 packages fails WACK for CLRCompression on x64 #19163
Comments
@ericstj @weshaggard will .NET Native customers automatically pick up the 1.1 libraries via UWP Meta package NuGet update? |
It's happening from folks who pick up the 1.1 packages either directly or indirectly (eg from an EntityFramework package that references the 1.1 packages). This is a must fix, we'd service for this, just like we serviced for similar problems in 1.0. |
I double checked if there were any other similar instances where folks were doing "external" build shenanigans and couldn't find any other cases. |
Another consideration: this one could be fixed through repackaging if you want to avoid a rebuild. |
Thanks for the fix @ericstj! |
Hi @ericstj I am facing same issue with my app Binary analyzer I have tried with compile with .net native tool chain and as well as with x86, x64 I am using windows 10 SDK 17134. I can find any solution. Below are the packages used in this app.
|
It’s not clear this is the same issue. Can you open a new issue with repro steps and attach the project.assets.json file? |
Hi @ericstj thanks for looking it. Its is difficult to reproduce the issue. I have attached project.assets.json. |
Created new issue https://github.com/dotnet/corefx/issues/30594 |
Copied from dotnet/efcore#6905
The aot clrcompression build is supposed to be redistributed from 1.0 while the non-aot build is being built live. When this change was made, the incorrect RID was used for x64-aot, causing the non-aot build to be picked up, which fails the WACK.
The fix here is to correctly list the RID as win10-x64-aot.
The text was updated successfully, but these errors were encountered: