You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
warning : NU5128: Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below: [d:\a\1\s\src\CI\CI.csproj]
Add a dependency group for .NETStandard2.0 to the nuspec
According to the documentation, this is a warning that didn't exist in previous versions of NuGet and seems to be related to using the new tools. The docs also offer a couple of options to remove this warning. We should figure out how to address this warning so that our builds are as clean as possible.
The text was updated successfully, but these errors were encountered:
This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!
Addresses Issue microsoft#335 - [ENG] Warning NU5128 in builds
This change should match the target frameworks of the dependencies specified in the nuspec file to the frameworks of the assemblies contained in the nuget package.
Addresses Issue #335 - [ENG] Warning NU5128 in builds
This change should match the target frameworks of the dependencies specified in the nuspec file to the frameworks of the assemblies contained in the nuget package.
Please check whether the bug has already been filed.
Describe the bug
Starting with commit 17c1319, we're getting the following warning during PR builds and signed builds
warning : NU5128: Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below: [d:\a\1\s\src\CI\CI.csproj]
According to the documentation, this is a warning that didn't exist in previous versions of NuGet and seems to be related to using the new tools. The docs also offer a couple of options to remove this warning. We should figure out how to address this warning so that our builds are as clean as possible.
The text was updated successfully, but these errors were encountered: