You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2019. It is now read-only.
PASH /> New-ModuleManifest
Command 'New-ModuleManifest' not found.
+CategoryInfo: ObjectNotFound, Reason: ParentContainsErrorRecordException
+FullyQualifiedErrorId: CommandNotFoundException
PASH />
PASH /> Get-Module -ListAvailable
No parameter was found that matches the name or alias 'ListAvailable'.
+CategoryInfo: InvalidArgument, Reason: ParameterBindingException
+FullyQualifiedErrorId: ParameterNotFound
PASH />
The text was updated successfully, but these errors were encountered:
We don't have a (graphical) interface to create manifest, yet (as New-ModuleManifest). But you can just write some in an editor, as in this example.
Note that a manifest is optional for simple script & binary modules.
Get-Module -ListAvailable doesn't work yet, as the results of the discussion of #332 haven't been integrated yet, so Pash doesn't know where to look for modules. But this is on my TODO list ;)
For now, you can import modules by using the absolute or relative path to the module location.
http://www.darkoperator.com/blog/2013/2/19/powershell-basics-extending-the-shell-with-modules-and-snapi.html
is it possible at all? ( yes, probably, since 2015-01-06 - #331 , #332 )
works, but doesn't show anything...
This tutorial doesn't work:
https://www.simple-talk.com/sysadmin/powershell/an-introduction-to-powershell-modules/
The text was updated successfully, but these errors were encountered: