Tool intended to help visualize all of the nuget packages and their corresponding versions for a set of given repositories
Initially, the data must be harvested. This can be done via the file system or by using the github API.
A console app is provided for testing purposes (and can be used as code examples on how to use)
The data can be harvested from the Harvest menu on the web.
Once the data is harvested, it can be visualized All data is stored in a Sqlite database
The harvesting process looks for .sln files in the hierarchy, and creates a Project for each solution. Then it looks for packages.config files in all children directories and associates those packages with the project, creating new Packages each time a new one (package name + version) is found. .net core 2.0+ projects are also supported, a different parser looks into csproj files
The Github API has several limitations. For example, it only allows 30 code search requests per minute, and it also limits the number of requests per IP address. This means that some throttling needs to be done to avoid the Github API from bouncing off requests when reading large repositories.
In order to minimize this effect, consider using filters when harvesting to reduce the returned results.
The solution is built and requires .net Core 2.0 to run
A configuration.json file must be created to run the tests and the application. The following variables are supported:
The database is initially created when the console app or website runs, it is created under the path defined by the Dbpath variable
Create a file named configuration.json in the root of ConsoleVisualizer folder, and also for the WebVisualizer. This can be used as a template:
{ "GithubOrganization": "YOUR ORGANIZATION HERE",
"GithubToken": "YOUR GITHUB TOKEN HERE",
"Dbpath" : "C:\\FullPathToSqlLiteDatabase\\myDatabase.db"
}
Just run them normally. At the moment of writing, Resharper's test runner doesn't work on .net core, so use the visual studio test runner. The Integration Tests that connect to github cannot be run locally, because a token is needed for a dummy organization i've created. Github doesn't let me check in tokens into source control for security reasons, so these tests run only on the travis build.
Go into /NugetVisualizer an run the following commands
Snapshot creation (data harvest) page
Once a Snapshot is created, data can be appended to it (make sure you're not adding the same repositories twice though)
Example dashboard with widgets (more to come in future versions)
Main page where the packages are ordered by distinct versions count and we can see which repository uses which version
https://github.com/sqlitebrowser/sqlitebrowser/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4
