search

goenning / dotnet-outdated

Command line tool to check for outdated DotNet Core dependencies.
MIT License
46 stars 6 forks source link

Some 'troublesome' packages #6

Open vegar opened 7 years ago

vegar commented 7 years ago

First: Great project! Love the output! Just what I wanted - except that I need it for 'legacyc' .net apps... After stealing most of your code and made it work with regular .net apps, I got errors fetching information on some dependencies of mine.

In NuGetClient you check for 'paged' version listings. If there are multiple items listings, you assume that multiple batches of versions needs to be fetched. But for NLog the batches are included in the first request for some reason.

There are other examples of this, like RazorEngine and NewRelicWindowsAzure.

Another strange package, is the WebActivator package. This listing has no version marked as "listed": true. That leads to the status.WantedVersion in DependencyStatus never being set, ending up with a Value can not be null when comparing dependency.CurrentVersion and status.WantedVersion.

Again - both a great and a needed tool! I'll probably modify it further to consolidate multiple project in a solution as well.

joelverhagen commented 6 years ago

@vegar, you are using registration1 which was deprecated long ago. Check out registration3 or registration3-gz-semver2: https://api.nuget.org/v3/registration3/webactivator/index.json

But note that WebActivator really has not listed versions. See the gallery page: https://www.nuget.org/packages/webactivator