-
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
Packing csproj with long description issues unresolvable warning about missing summary text #4587
Comments
@natemcmaster before we assign a milestone to this, just want to make sure this is not blocking you in any way? |
Not blocking. It's just a build warning, not an error. |
just an FYI, you can disable these warning by setting the |
Yeah we found that setting. We want to keep it enabled though just in case there are other package issues. Would be cool if we could turn off certain NuGet warnings but not all, but that would be a much bigger feature. |
will discuss possible options with @rrelyea |
For the MVC repo, would it be possible to make Or will the warnings be fixed soon? |
Is there a work-around to this issue until support of the summary field is added to csproj? Just ignoring the warning and having a truncated summary seems more than a little messy. |
@DavidArno understand that Description is not actually truncated in the nuspec file. It's only in the Visual Studio UI where the Description is too long it collapses it to fit the space, but a user can however click on ReadMore to read the rest of the Description |
I believe I heard somewhere that |
@AArnott |
the fix that we will do to close this bug is going to remove this warning for netcore projects. |
Can somebody comment here on what is supposed to go into NuGet. If NuGet has a |
long description produced warnings when running dotnet pack NuGet/Home#4587
The current solution is to disable package analysis. Do not shorten the description only for the sake of shortening it! Add this property to the project: <NoPackageAnalysis>true</NoPackageAnalysis> |
@rohit21agrawal, @natemcmaster: I suggest this issue be given more priority. the problem is a warning is generated during build, as of VS15.4.5 RTM:
Many links from this issue point to the developers trying to shorten the description of the package in their commits, and this is not a good thing (arguably it might be, but no shorter than necessary :)). The workaround is of course to disable package analysis; if it's possible to make the workaround more visible interim, that would be even better! |
Because the Summary field has been retired itself, per NuGet/Home#4587 (comment) dotnet/project-system#2937 (comment)
It's not actually possible to provide a summary right now as per NuGet/Home#4587
* squash SA1649 warnings (file/type name mismatch) * squash SA1127 warnings (generic constraint on own line) * squash SA1507 warnings (multiple blank lines) * squash package analysis warnings re: summary text It's not actually possible to provide a summary right now as per NuGet/Home#4587 * squash missing castle.core reference warning * squash obsolete method warnings re: AddOcelotBaseUrl
* squash SA1649 warnings (file/type name mismatch) * squash SA1127 warnings (generic constraint on own line) * squash SA1507 warnings (multiple blank lines) * squash package analysis warnings re: summary text It's not actually possible to provide a summary right now as per NuGet/Home#4587 * squash missing castle.core reference warning * squash obsolete method warnings re: AddOcelotBaseUrl
* squash SA1649 warnings (file/type name mismatch) * squash SA1127 warnings (generic constraint on own line) * squash SA1507 warnings (multiple blank lines) * squash package analysis warnings re: summary text It's not actually possible to provide a summary right now as per NuGet/Home#4587 * squash missing castle.core reference warning * squash obsolete method warnings re: AddOcelotBaseUrl
Packing a csproj with a long
<Description>
value issues the following warnings:However, specifying a Summary field is not possible from csproj.
Repro
Details
Using NuGet/Microsoft.NET.Sdk RC4
cc @rohit21agrawal
The text was updated successfully, but these errors were encountered: