-
Notifications
You must be signed in to change notification settings - Fork 427
Trimming fails for .NET Framework projects that use PackageReference #667
Comments
When I remove PrivateAssets="all", a separate PackageReference starts causing the same error even though it does not have PrivateAssets specified. |
Would repro projects help? |
I see what's happening. Updated the title of the bug and will put together a fix. |
Actually, hold up I may have spoken too soon. Which version of the SDK are you using? It's possible that this change went through and I need to react to it: #626 |
This is a .NET Framework project building in the Visual Studio 15.6.1 IDE. That makes sense. |
Got it. Reproducing now. The bug is due to missing the PackageDependency item completely in old NuGet targets, so similar to #626 but for a different reason. To workaround it you can set
This will turn of our package graph rooting completely, but you'll still get the binary graph rooting. I'll need to bring back lock/asstets file reading to get the package graph for this and #626. |
Great! I was looking for something like |
We have that here: https://github.com/dotnet/standard/blob/master/Microsoft.Packaging.Tools.Trimming/docs/trimming.md#additional-options though it could probably use some clean up (just reviewing now I see a number of typos). I'll make sure to give that some love when I address this issue as well. |
Silly of me, I think I saw that before and missed the significance of |
Fixed with #671 |
@ericstj Very cool! Is there something I can subscribe to in order to know when a new prerelease is published? |
Should be here: https://dotnet.myget.org/feed/dotnet-core/package/nuget/Microsoft.Packaging.Tools.Trimming. It builds daily, but I requested another build today since I missed this morning's sync point. |
Package is available: |
@ericstj The latest version available from NuGet is 1.1.0-preview1-25818-01 which still has this issue. Can we get a newer version into NuGet? |
Yes I will publish an update. |
Thanks! |
It is published now |
Thanks, that version solved the issue for me. I appreciate the help. |
The csproj has:
It fails to build, giving:
Is this expected to work?
The text was updated successfully, but these errors were encountered: