admin管理员组

文章数量:1355758

In the script module, with 98 ps1 filles. Each file had access to each cmdlet from each file without needing to explicitly export them.

But in the manifest module, only the cmdlets that have been explicitly exported in psd1 file can be accessed by each file. I renamed the files to psm1 and declared them in NestedModules

There are way too many cmdlets to export them all, especially if there is no external need.

How to get the same behavior in a manifested module?

In the script module, with 98 ps1 filles. Each file had access to each cmdlet from each file without needing to explicitly export them.

But in the manifest module, only the cmdlets that have been explicitly exported in psd1 file can be accessed by each file. I renamed the files to psm1 and declared them in NestedModules

There are way too many cmdlets to export them all, especially if there is no external need.

How to get the same behavior in a manifested module?

  • powershell
Share Improve this question asked Mar 28 at 19:34 deetledeetle 4312 silver badges13 bronze badges 2
  • ... not completely sure if I got what meant ... but you may use Get-ChildItem $psscriptroot\*.ps1 | ForEach-Object { . $_.FullName }; Export-ModuleMember -Function * -Alias * inside your *psm1 file and FunctionsToExport = '*' inside your *psd1 file. This way you include all single *.ps1 script files in you module and export all functions included in these script files.

    本文标签：

    版权声明：本文标题：powershell - Converting a script module to a manifest one. But each file doesn't have access to each cmdlet without expo 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1744016969a2576506.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。