This project can now be found on http://www.codeplex.com/vitoolkitextensions
says:
in response to: halr9000
Regarding export-modulemember, cmdlets appear to be global no matter what. I believe this is probably an oversight. Functions certainly have to be exported.
says:
Turns out the instructions were sitting in the "Author Discussion" tab, which was only visible to me. Sorry about that, here are the instructions:
(new-object net.webclient).DownloadString("http://communities.vmware.com/servlet/JiveServlet/downloadBody/6051-102-1-3481/Extensions.psm1") > $env:temp/Extensions.psm1 add-module $env:temp/Extensions.psm1
Updated instructions
(new-object net.webclient).DownloadString("http://communities.vmware.com/servlet/JiveServlet/downloadBody/6051-102-4-4112/Extensions.psm1") > $env:temp/Extensions.psm1
add-module $env:temp/Extensions.psm1
Unfortunately this changes with every rev 
We'll have a better process in place before long.
(Note: this requires PowerShell V2 CTP 2.)
I haven't tried these yet but these look very interesting: SVMotion-VM, Get-DatastoreFiles, Register-VM. Good stuff.
Can .psm1 files be used this way? I thought you had to use the Export-ModuleMember cmdlet in order to have these things appear in the correct scope. I could be wrong, have not messed much with modules as of yet.
I do like that you are pushing the bleeding edge though.
Hal Rottenberg
Co-Host, PowerScripting Podcast (http://powerscripting.net)