Skip to content
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

SponsorLink warnings in VS builds that can't be suppressed and "build paused for Xms"? #371

Closed
Sergio0694 opened this issue Apr 1, 2023 · 1 comment · Fixed by #381
Closed
Labels
bug Something isn't working

Comments

@Sergio0694
Copy link

Overview

After updating NuGetizer recently, I've noticed a bunch of messages like these in VS builds:

Contrary to messages like eg. DNG02, which can easily be suppressed, I couldn't find a way to suppress this one. Additionally, what's that "build paused for Xms" message? That doesn't sound encouraging. Regardless, I'm totally fine with people trying to incorporate more ways to push developers into doing sponsorship and it's of course their right, but that's not the approach I personally like and want to have in my build setup, nor one I would want others depending on my library to use. People can sponsor me if they like, and that's of course welcome, but I wouldn't want to inject anything like this into their build infrastructure. My issue is also with the fact that regardless of whether one is actually sponsoring or not, I wouldn't want them to have to then do more work to setup all the necessary stuff in their solution to prove they did actually sponsor the project, so that the analyzer/targets can finally stop showing warnings.

Is there a way to completely suppress these warnings? I'm not asking to make any changes in this or related project, since as I said, of course anyone's free to do whatever they prefer. I'm just asking because if there is a way, I'd very happily just enable that. If not, I think I'll just remove the NuGetizer dependency entirely and just use a vanilla SDK-style .csproj to configure the packages I have.

Thank you! 🙂

@kzu
Copy link
Member

kzu commented Apr 18, 2023

Hi @Sergio0694 , thanks for your feedback! Please see https://www.cazzulino.com/sponsorlink.html for background on why I'm doing this and how it works.

nor one I would want others depending on my library to use

Your library doesn't have a dependency on NuGetizer (or transitively, SponsorLink), since nugetizer is a development dependency. So nobody using your library will ever hear about SponsorLink.

The warning you're seeing is for you: as a developer taking advantage of NuGetizer, I'm asking you to sponsor me so I can continue working on it, improving it and fixing issues.

Does that clarify what you're seeing?

kzu added a commit that referenced this issue Apr 19, 2023
@kzu kzu closed this as completed in #381 Apr 19, 2023
kzu added a commit that referenced this issue Apr 19, 2023
@devlooped devlooped locked and limited conversation to collaborators Nov 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants