-
Notifications
You must be signed in to change notification settings - Fork 446
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
Dependencies of netfx PackageReferences aren't referenced #78
Comments
Does the nuspec rendering of the package to package dependencies have exclude=compile? Do you have a repro using packages that we can access? |
@jnm2 Friendly ping on those questions. If there are exclude=compile in the nuspecs of these packages, this is by design. If they do not, I'll need a repro to investigate further. |
Duplicate of NuGet/Home#5957 |
@nguerrera I'm so sorry I didn't get to this. Glad it was an existing problem and not something new. |
No problem! I happened upon that nuget issue and then it hit me that this is the same as that. |
I'm referencing DevExpress's NuGet packages which target
net40
in anetcoreapp3.0
project using<FrameworkReference Include="Microsoft.DesktopUI" />
. NuGet gives a warning but everything should restore fine. From BUILD and dotnetconf, the expectation is that many .NET Framework assemblies actually do just work for the time being.However, the compiler isn't referencing any assemblies from the package dependencies of these packages. In order to get the compiler to see assemblies in the package graph, I have to directly reference every package in the tree.
These packages come from a private feed with DevExpress customer API token in the URL, but there's nothing unusual about them.
Here's the workaround for now:
The text was updated successfully, but these errors were encountered: