Centralized Package Management for Power Shell
Votes from Connect: 11
Original Date Submitted: 9/10/2013 2:56:23 AM
Site Name: PowerShell
Feedback ID: 800050
Frequency: Always Happens
Regression: Yes, this happens in all previous versions
Centralized Package Management would be a huge win for PowerShell. Modules are a great part of PowerShell, but writing scripts for other people/computers that depend on them can be problematic, as you can't guarantee that the modules will be installed on those computers. If PowerShell had something similar to Ruby Gems that would be great, where at the top of the script you specify the modules that the script depends on, and if they aren't installed on the current PC already then they are automatically downloaded and installed.
This would encourage more people to write reusable modules, and would avoid people copy/pasting multiple files/modules into a single script file, or having to zip up the whole suite of scripts that a script depends on when distributing it to other people/computers.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 800050 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=800050).
Try and run a script that depends on a module on a fresh PC, and the script will fail because it cannot find the dependent module.
The script should automatically connect to the Internet to download and install the module.
Internal BugId: 5375