Managing dependencies of Powershell modules -
i have custom powershell script module, let's call pshandycmdlets
. in manifest following line found: requiredmodules = @('<another module not installed yet>')
the requiredmodules
property supposed guarantee module listed here imported global scope before importing current module. fail if module can't located on machine.
does powershell provide mechanism ensuring these modules installed when pshandycmdlets
installed? if there isn't, there best practice in place handling scenario?
Comments
Post a Comment