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!
ProGet - Filter connectors by package version
-
Hi,
We are just wondering if there is any plan to be able to filter specific versions of packages from connected feeds? We have just a couple of public packages the we use, that we know have a version or two that actually aren't working properly. For example Castle.Core 2.5.2.0 (I think these version numbers are correct btw), actually contains Castle.Core 2.5.1.0 assembly and has broken builds a couple of times.
This obviously is a niche feature so we're not really expecting it to be available, but perhaps others have had the same problem, we weren't sure.
Thanks once again,
Adam. -
We wanted to include versions in our Connector Filters, but it wasn't really practical. If memory serves correctly, NuGet's ODATA implementation sees version numbers as strings, thus you couldn't do version ranges or anything like that.
I think someone on our team submitted an issue to NuGet about this, but as far as I know it's still treated as strings.
So, until then, your best bet is to manually craft your feed. One trick someone suggested was to create a feed with a connector to nuget.org and then download packages to a "Allowed NuGet PAckages" feed (no connectors) --- both of which share the same local directory.
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