-
Notifications
You must be signed in to change notification settings - Fork 258
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
NU5131 issues #8684
Comments
I think it's perfectly acceptable to create packages which are only compatible with PackageReference (hence using the ref folder). Right now this is too noisy and defeats the user trust in the warning. |
Just noticed this. The warning shouldn't force people to use the |
Hi,
My nuspec file looks like this: <dependencies>
<group targetFramework="net5.0-windows">
</group>
</dependencies>
</metadata>
<references>
<group targetFramework="net5.0-windows">
<reference file="MyAssembly.dll" />
</group>
</references>
... The Nuget is created and I am able to successfully use it. But - Any suggestion as to how I can fix these warnings? |
NU5131 was added to try to encourage packages that select which assemblies are used by projects to work with both
packages.config
andPackageReference
.We are currently aware of two issues:
Packages build from MSBuild (no nuspec)
A project that puts a file in
ref/<tfm>/
will trigger the warning, therefore asking the package author to create a<references>
element in the nuspec. However, the MSBuild pack tasks doesn't provide a way to specify it.Missing runtime files
See #3830.
The text was updated successfully, but these errors were encountered: