Consider adding a preference variable to allow v1 style snapins to behave as binary modules
Votes from Connect: 16
Original Date Submitted: 12/10/2011 12:34:32 AM
Handle: Oisin Grehan
Site Name: PowerShell
Feedback ID: 712798
Frequency: Always Happens
Regression: Yes, this happens in previous released versions
Currently we have to treat snapins and modules differently in powershell. Registered snapins won't show up in the output of get-module -listavailable. I would like to see a preference variable added that would allow snapins to be listed, loaded and unloaded with the module cmdlets. For example, the quest AD snapin, the TFS power tools etc don't show up in the output of get-module -list as they are registered as snapins using installutil.
I would imagine it would not be too hard to autogenerate a stub module manifest from the snapin assembly metadata, or failing that, just load the snapin assembly directly with the get-module code path.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 712798 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=712798).
Internal BugId: 3187