Simple Tool for checking NuGet Dependencies and publish a report as build artifact. The results will be added to a new build tab and can be saved as build artifact. (no dashboard widget yet, but i will work on it!).
Feel free to submit pull requests for new features!
First add the root directory of the project as Searchpath. This is usually $(Build.SourcesDirectory). If you also check the Search Recursive box all packages.config files will be analyzed.
Now you can say if you want to create a badge and if to create a report. The destination or the reportfile is very important. By default it will be created in the $(Build.ArtifactStagingDirectory) directory. Another build tasks has to handle this file. Ex. copy it to a webserver. Depending on your infrastructure you can also do this directly by \\yourserver\yourshare\dependencies.html. Just do the same with the badge path.
Path to check for the packages.config files.
Search subdirectories for the packages files.
This option will combine all found projects and lists all packages in a distincted form. If a package is installed several times, it will be listed seperatly. This option is similar to Visual Studios "Consolidation" function
Include prerelease packages for search?
Define your custom NuGet config which has additional sources.
Create a badge using DotBadge.
If selected, a badge will be created for every single project found. If not selected, the information of all projects will be aggregated and "the worst" will be generated.
Where to save the badge and its name. (only available if only one badge needs to be generated)
Path of the directory where the badges should be generated (only available if multiple badges should be generated)
The style of the badge.
Create a report of the packages.
Location and name where to save report.
The buld pipeline is automaticly triggered for all commits in this Repo. The pipeline generates a new preview extension which can be used for testing.
Pipeline runs from the master branch will be deployed automaticly to the public extension registry.
Assemblies and task are versioned according to the last published extension version by increasing the version number.
If you are forking this repo are creating a PR, the pipeline will not publish the extension to the marketplace.
Following open source libraries are used for this little project. Thank you for your great work!