Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Automatically Cache nuget packages

    Scheduled Pinned Locked Moved Support
    proxyproget
    4 Posts 1 Posters 34 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Is there a way to configure ProGet to cache proxied nuget.org packages the first time it gets installed in my project? I noticed that you have to manually log into ProGet and click the “download” button on a nuget package to actually have it available in the cache. That is not ideal for us.

      Product: ProGet
      Version: 3.3.12

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        You shouldn't have to go to the web UI for that; any package that is downloaded from a connector when the feed is set to cache packages will cache them.

        You can see it in the web UI on the package details page where it says:

        Package Source
        Remote Connector (cached)

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          If this is the case, then why do I still see a button saying "Pull to ProGet" next to a nuget package that I have downloaded from a connector via Package Control Manager in VS.NET? I would expect that button to not be there anymore.

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            A "cached" package is a package that's stored locally so it doesn't have to be downloaded from the external feed, as opposed to a "local package" which is a package that is actually in the local feed. Packages are cached the first time they are requested from the external feed (whether that's by downloading it in the UI, or by using nuget restore, or downloaded via some other tool).

            Pulling a package downloads a remote package into the local feed as if you pushed it to the feed yourself, so to speak.

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post
            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation