PowerShell Module Deployment
I don't know which profile location my users are going to deploy my module to. How can I define RootModule path in the manifest?
For example, one user may deploy the module to the PS Profile folder under System32 (All Users) and another may deploy it to the PS Profile folder under his Windows user profile (Current User).
This means the .psd1 file will need to be manually edited after a user deploys my module. Is there any way around this problem (aside from writing a compiled installer)?
powershell module manifest
asked Nov 11 '18 at 5:57
dev19dev19
1
add a comment |
I don't know which profile location my users are going to deploy my module to. How can I define RootModule path in the manifest?
For example, one user may deploy the module to the PS Profile folder under System32 (All Users) and another may deploy it to the PS Profile folder under his Windows user profile (Current User).
This means the .psd1 file will need to be manually edited after a user deploys my module. Is there any way around this problem (aside from writing a compiled installer)?
powershell module manifest
asked Nov 11 '18 at 5:57
dev19dev19
1
add a comment |
I don't know which profile location my users are going to deploy my module to. How can I define RootModule path in the manifest?
For example, one user may deploy the module to the PS Profile folder under System32 (All Users) and another may deploy it to the PS Profile folder under his Windows user profile (Current User).
This means the .psd1 file will need to be manually edited after a user deploys my module. Is there any way around this problem (aside from writing a compiled installer)?
powershell module manifest
asked Nov 11 '18 at 5:57
dev19dev19
1
I don't know which profile location my users are going to deploy my module to. How can I define RootModule path in the manifest?
For example, one user may deploy the module to the PS Profile folder under System32 (All Users) and another may deploy it to the PS Profile folder under his Windows user profile (Current User).
This means the .psd1 file will need to be manually edited after a user deploys my module. Is there any way around this problem (aside from writing a compiled installer)?
powershell module manifest
powershell module manifest
asked Nov 11 '18 at 5:57
dev19dev19
1
asked Nov 11 '18 at 5:57
dev19dev19
1
asked Nov 11 '18 at 5:57
dev19dev19
1
asked Nov 11 '18 at 5:57
dev19dev19
1
asked Nov 11 '18 at 5:57
dev19dev19
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is no RootModule path in the manifest file. Only a RootModule which is set to the name of your psm1-module.
microsoft:
Script module or binary module file associated with this manifest. Previous versions of PowerShell called this element the ModuleToProcess.
Possible types for the root module can be empty (which will make this a Manifest module), the name of a script module (.psm1, which makes this a Script module), or the name of a binary module (.exe or .dll, which makes this a Binary module). Placing the name of a module manifest (.psd1) or a script file (.ps1) in this element will cause an error to occur.
Base on what you described it seems that you need an absolute path in your module. If so, use the $PSScriptRoot in your module. Check this link.
Hope that helps.
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The solution was to correct the PSModulePath$env:PSModulePathon my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.
– dev19
Nov 11 '18 at 17:34
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246240%2fpowershell-module-deployment%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no RootModule path in the manifest file. Only a RootModule which is set to the name of your psm1-module.
microsoft:
Script module or binary module file associated with this manifest. Previous versions of PowerShell called this element the ModuleToProcess.
Possible types for the root module can be empty (which will make this a Manifest module), the name of a script module (.psm1, which makes this a Script module), or the name of a binary module (.exe or .dll, which makes this a Binary module). Placing the name of a module manifest (.psd1) or a script file (.ps1) in this element will cause an error to occur.
Base on what you described it seems that you need an absolute path in your module. If so, use the $PSScriptRoot in your module. Check this link.
Hope that helps.
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The solution was to correct the PSModulePath$env:PSModulePathon my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.
– dev19
Nov 11 '18 at 17:34
add a comment |
There is no RootModule path in the manifest file. Only a RootModule which is set to the name of your psm1-module.
microsoft:
Script module or binary module file associated with this manifest. Previous versions of PowerShell called this element the ModuleToProcess.
Possible types for the root module can be empty (which will make this a Manifest module), the name of a script module (.psm1, which makes this a Script module), or the name of a binary module (.exe or .dll, which makes this a Binary module). Placing the name of a module manifest (.psd1) or a script file (.ps1) in this element will cause an error to occur.
Base on what you described it seems that you need an absolute path in your module. If so, use the $PSScriptRoot in your module. Check this link.
Hope that helps.
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The solution was to correct the PSModulePath$env:PSModulePathon my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.
– dev19
Nov 11 '18 at 17:34
add a comment |
There is no RootModule path in the manifest file. Only a RootModule which is set to the name of your psm1-module.
microsoft:
Script module or binary module file associated with this manifest. Previous versions of PowerShell called this element the ModuleToProcess.
Possible types for the root module can be empty (which will make this a Manifest module), the name of a script module (.psm1, which makes this a Script module), or the name of a binary module (.exe or .dll, which makes this a Binary module). Placing the name of a module manifest (.psd1) or a script file (.ps1) in this element will cause an error to occur.
Base on what you described it seems that you need an absolute path in your module. If so, use the $PSScriptRoot in your module. Check this link.
Hope that helps.
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
There is no RootModule path in the manifest file. Only a RootModule which is set to the name of your psm1-module.
microsoft:
Script module or binary module file associated with this manifest. Previous versions of PowerShell called this element the ModuleToProcess.
Possible types for the root module can be empty (which will make this a Manifest module), the name of a script module (.psm1, which makes this a Script module), or the name of a binary module (.exe or .dll, which makes this a Binary module). Placing the name of a module manifest (.psd1) or a script file (.ps1) in this element will cause an error to occur.
Base on what you described it seems that you need an absolute path in your module. If so, use the $PSScriptRoot in your module. Check this link.
Hope that helps.
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
answered Nov 11 '18 at 7:18
MoerwaldMoerwald
2,86041440
2,86041440
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The solution was to correct the PSModulePath$env:PSModulePathon my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.
– dev19
Nov 11 '18 at 17:34
add a comment |
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The solution was to correct the PSModulePath$env:PSModulePathon my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.
– dev19
Nov 11 '18 at 17:34
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The value I was using for RootModule was the full path to the .psm1, which of course would be different depending on which PS profile folder (Current User or All Users) the module folder was copied to.
– dev19
Nov 11 '18 at 17:19
The solution was to correct the PSModulePath
$env:PSModulePath on my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.– dev19
Nov 11 '18 at 17:34
The solution was to correct the PSModulePath
$env:PSModulePath on my test workstation. By default, PSModulePath should include both Current User and All Users profile folders. While the value for RootModule can be the full path to the .psm1, it does not need to be. Instead, it should be simply the name of the module folder if the location to which the module folder is deployed in the PSModulePath.– dev19
Nov 11 '18 at 17:34
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246240%2fpowershell-module-deployment%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
