Nuget cross-feed dependencies in web interface

[m.karing_2439]

Hello,

I am using two nuget feeds right now in my setup. One is for all our internal packages, the other one is connected to a few public feeds including nuget.org and works as a cache.

Now we got some packages in our internal feed, that have dependencies that are part of the public feed. They are correctly displayed in the list of dependencies for the specific package, but the link is pointing to the internal feed that does not contain the public packages. This results in the link being invalid. Clicking it results in a HTTP 404 error and records an error in the error log page.

Is there any way to get those links to work and reference the public repository if required? I don't really want to setup a connector and have the public images pulled over into the internal feed.

Best regards,
Martin

[stevedennis]

Hi @m-karing_2439 ,

The link on the "Dependencies" is provided for convenience; it's simply wrapping a <a href=... around items in the .nuspec file's Dependencies element. Without performing expensive lookups, there is no way to know if those packages are in the current feed, or if they're even valid packages or versions at all.

Keep in mind that, in many cases, dependencies won't even reference a single package (e.g. MyPackage-4.8.7) - but a whole range of versions (e.g. MyPackage-4.*). This is why it's impossible for ProGet (or any tool) to "resolve" the dependencies - it requires knowing all packages in project (plus the project's environmental configuration) to know which ranges to pick.

Note that, if those links yield a 404 then clients will also not be able to download them from thet feed.

Thanks,
Steve