For project dependencies:
I would love to see a dependency chain of all my packages.
Step 1: I would like to be able to click on a package and see what packages depend on it in my project. So if I click on jQuery, I would see that jQueryUI and jQuery Validation depend on it. This would prevent developers from trying to uninstall packages that they think aren't being used, but really are.
Step 2: I would like to see all the projects that don't have any dependencies on them. These would hint to the developer which ones may or may not be being used. So let's say the list included Package X. Then I could check to see if Package X was actually being used and if not, remove it, which would potentially show me other packages that weren't being used.
Step 3. I would like this info output to a text document (or possibly in the packages.config) so that developers can keep track of which packages are leaf nodes. This way if a new package ends up as a leaf, possibly due to Package A replacing a dependency on Package B with Package C, the developers would see that there is a package that needs to be investigated to see if it is still needed.
Just some thoughts,
Dan
I would love to see a dependency chain of all my packages.
Step 1: I would like to be able to click on a package and see what packages depend on it in my project. So if I click on jQuery, I would see that jQueryUI and jQuery Validation depend on it. This would prevent developers from trying to uninstall packages that they think aren't being used, but really are.
Step 2: I would like to see all the projects that don't have any dependencies on them. These would hint to the developer which ones may or may not be being used. So let's say the list included Package X. Then I could check to see if Package X was actually being used and if not, remove it, which would potentially show me other packages that weren't being used.
Step 3. I would like this info output to a text document (or possibly in the packages.config) so that developers can keep track of which packages are leaf nodes. This way if a new package ends up as a leaf, possibly due to Package A replacing a dependency on Package B with Package C, the developers would see that there is a package that needs to be investigated to see if it is still needed.
Just some thoughts,
Dan