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!

    NuGet packages older .NET versions not visible

    Scheduled Pinned Locked Moved Support
    proget
    4 Posts 2 Posters 3 Views 1 Watching
    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.
    • Y Offline
      ygeelen-tb
      last edited by

      It seems that NuGet packages that were built for .NET 4.0 for example, are not queryable/visible in the NuGet Package Manager extension of Visual Studio for projects that target a higher .NET version (like 4.6) for ProGet feeds.
      We noticed this issue when trying to install a package from nuget.org and from our ProGet feed connector to nuget.org.

      Product: ProGet
      Version: 3.7.5

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

        It's hard to say without seeing the specific queries; framework targeting is really strange and has a lot of edge cases... it's also possible it's been updated since v3.7.5.

        I would suggest to upgrade to the latest ProGet, then if it still doesn't work, can you the identify specific packages and the specific queries (via fiddler) that are behaving differently then on nuget.org?

        1 Reply Last reply Reply Quote 0
        • Y Offline
          ygeelen-tb
          last edited by

          I've upgraded to the latest version "Version 4.0.10 (Build 1)". The issue seems to be solved for the package Geocoding.net.

          For our feed with inhouse developed packages the issue persists..
          Packages with a "lib/net40" folder structure are visible, while any packages with a "lib/net451" folder structure are not ?

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

            We will explore this further; NuGet 3.4 added new abbrebrivations that we will be supporting in the next maintenance release.

            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