Comments on: PowerShell Modules http://huddledmasses.org/powershell-modules/ You can do more than breathe for free... Fri, 03 Feb 2012 03:27:25 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: The PowerShell Guy : PowerTab for PowerShell V2 Alpha testers wanted http://huddledmasses.org/powershell-modules/comment-page-1/#comment-174230 The PowerShell Guy : PowerTab for PowerShell V2 Alpha testers wanted Mon, 14 Jul 2008 18:35:54 +0000 http://HuddledMasses.org/?p=543#comment-174230 [...] for the rest as it is a Module now  the installation is very simple, follow Jaykul's excellent intro here : PowerShell Modules [...] [...] for the rest as it is a Module now  the installation is very simple, follow Jaykul’s excellent intro here : PowerShell Modules [...]

]]> By: Joel 'Jaykul' Bennett http://huddledmasses.org/powershell-modules/comment-page-1/#comment-170983 Joel 'Jaykul' Bennett Sat, 05 Jul 2008 02:13:19 +0000 http://HuddledMasses.org/?p=543#comment-170983 If you're interested in more information about Microsoft's intentions for modules ... Bruce made a presentation at the Virtual PowerShell User Group about modules, and "uploaded his slide deck":http://cid-18d901b0daff5738.skydrive.live.com/self.aspx/Public/UG6/Windows%20PowerShell%20Version%202%20Modules.pptx ... which was very interesting, and focused on "post-CTP2 functionality" (meaning a lot of it doesn't work in the build you have now). He did say plainly that Modules are intended to *replace* Snapins, and gave some details about using PowerShell data files (.psd1) for module loading (although I _still_ can't get that to work in CTP2) ... I could really dig getting some help files for these cmdlets and functionality, or maybe a new release with some of the bug fixes they've already put in ;-) If you’re interested in more information about Microsoft’s intentions for modules … Bruce made a presentation at the Virtual PowerShell User Group about modules, and uploaded his slide deck … which was very interesting, and focused on “post-CTP2 functionality” (meaning a lot of it doesn’t work in the build you have now).

He did say plainly that Modules are intended to replace Snapins, and gave some details about using PowerShell data files (.psd1) for module loading (although I still can’t get that to work in CTP2) ... I could really dig getting some help files for these cmdlets and functionality, or maybe a new release with some of the bug fixes they’ve already put in ;-)

]]> By: karl prosser http://huddledmasses.org/powershell-modules/comment-page-1/#comment-159701 karl prosser Wed, 28 May 2008 04:57:12 +0000 http://HuddledMasses.org/?p=543#comment-159701 good article joel good article joel

]]> By: Joel 'Jaykul' Bennett http://huddledmasses.org/powershell-modules/comment-page-1/#comment-159683 Joel 'Jaykul' Bennett Wed, 28 May 2008 02:11:54 +0000 http://HuddledMasses.org/?p=543#comment-159683 I had wondered about a system package path, but I couldn't find a way to figure out the defaults, and I did discover (quite accidentally) that if you don't export, everything is exported. The plans for the future sound awesome! I "filed":https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=346438&SiteID=99 "a few":https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=346423&SiteID=99 "bugs":https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=346420&SiteID=99 "this afternoon":https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=346371&SiteID=99 "too":https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=346691&SiteID=99 ... I had wondered about a system package path, but I couldn’t find a way to figure out the defaults, and I did discover (quite accidentally) that if you don’t export, everything is exported.

The plans for the future sound awesome! I filed a few bugs this afternoon too …

]]> By: Bruce Payette http://huddledmasses.org/powershell-modules/comment-page-1/#comment-159661 Bruce Payette Wed, 28 May 2008 00:35:03 +0000 http://HuddledMasses.org/?p=543#comment-159661 Hi Jay Here are some quick notes on your post. Yes, modules are the new snapins (though the snapin mechanism will remain for backwards compatibility.) We intend to support xcopy install of PowerShell extensions, either script or dlls. BTW - the default package path also includes $PSHOME/packages/ (i.e. there are user and system package directories) The module implementation is not complete in CTP2. This is why remove doesn't do what you expect. Also, we're planning to just use the term "module" in the final product instead of modules and packages.) If Export-ModuleMember is not used in a module, then by default all functions are exported from the script. If Export-ModuleMember is used at the top level of a session, then it will constrain the top level. In other words, after running Export-Module member, the only functions you can use are the ones you exported. (Cmdlets are currently not constrained by this mechanism.) We will be adding additional support to allow you to also control aliases and variable exports. -bruce Hi Jay

Here are some quick notes on your post.

Yes, modules are the new snapins (though the snapin mechanism will remain for backwards compatibility.) We intend to support xcopy install of PowerShell extensions, either script or dlls.

BTW – the default package path also includes $PSHOME/packages/ (i.e. there are user and system package directories)

The module implementation is not complete in CTP2. This is why remove doesn’t do what you expect. Also, we’re planning to just use the term “module” in the final product instead of modules and packages.)

If Export-ModuleMember is not used in a module, then by default all functions are exported from the script.

If Export-ModuleMember is used at the top level of a session, then it will constrain the top level. In other words, after running Export-Module member, the only functions you can use are the ones you exported. (Cmdlets are currently not constrained by this mechanism.) We will be adding additional support to allow you to also control aliases and variable exports.

-bruce

]]>