What are the pros and cons of publishing NuGet packages publicly and privately?

Question

I've been scouring the web for this question: What are the pros and cons of both publishing NuGet packages publicly and privately? It've not been successful in this endeavor, after lots of searching. I did find a whitepaper by Microsoft but nothing like what I'm looking for. I can guess what these pros and cons are but I'd like to see a response/reply from pros on this subject. Thanks.

Answer 1

Hi @Michael Gonzalez (Contractor) ,

Welcome to Microsoft Q&A!

Rather than talking about the pros and cons of public and private packages, it is better to understand the difference and choose according to your needs:
• Public packages are made available to all developers globally through nuget.org (requires NuGet 4.1.0+).
• Private packages are available to only a team or organization (a limited audience), by hosting them either a file share, a private NuGet server, Azure Artifacts, or a third-party repository such as myget, ProGet, Nexus Repository, and Artifactory.

You can refer to: Publishing packages.

Sincerely,
Anna
*
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.