Mixing
Invoking custom cmdlet from script block in PowerShell
I'm very new to PowerShell. I wrote a cmdlet which works fine. However, when I try and invoke it inside a job...
. .MyCmdlet.ps1 # Dot Source
$GetProcesssJob = Start-Job -ScriptBlock {
MyCmdlet
} -Credential $specialCredentials
...I get the error that it's "not recognized as the name of a cmdlet, function, script file, or operable program". What am I doing wrong?
powershell cmdlet start-job
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
add a comment |
I'm very new to PowerShell. I wrote a cmdlet which works fine. However, when I try and invoke it inside a job...
. .MyCmdlet.ps1 # Dot Source
$GetProcesssJob = Start-Job -ScriptBlock {
MyCmdlet
} -Credential $specialCredentials
...I get the error that it's "not recognized as the name of a cmdlet, function, script file, or operable program". What am I doing wrong?
powershell cmdlet start-job
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
2
The*-Jobcmdlets start a new runspace so things you load in your existing session do not exist there. Dot-source yourMyCmdletscript in the scriptblock forStart-Job
– TheIncorrigible1
Nov 22 '18 at 0:19
I had actually tried that and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access to the file MyCmdlet.ps1!
– ThisRestlessPilgrim
Nov 22 '18 at 0:28
You might be able to use-InitializationScript- I'm unsure what context that gets run in.
– TheIncorrigible1
Nov 22 '18 at 0:29
add a comment |
I'm very new to PowerShell. I wrote a cmdlet which works fine. However, when I try and invoke it inside a job...
. .MyCmdlet.ps1 # Dot Source
$GetProcesssJob = Start-Job -ScriptBlock {
MyCmdlet
} -Credential $specialCredentials
...I get the error that it's "not recognized as the name of a cmdlet, function, script file, or operable program". What am I doing wrong?
powershell cmdlet start-job
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
I'm very new to PowerShell. I wrote a cmdlet which works fine. However, when I try and invoke it inside a job...
. .MyCmdlet.ps1 # Dot Source
$GetProcesssJob = Start-Job -ScriptBlock {
MyCmdlet
} -Credential $specialCredentials
...I get the error that it's "not recognized as the name of a cmdlet, function, script file, or operable program". What am I doing wrong?
powershell cmdlet start-job
powershell cmdlet start-job
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
asked Nov 22 '18 at 0:13
ThisRestlessPilgrimThisRestlessPilgrim
86112
86112
2
The*-Jobcmdlets start a new runspace so things you load in your existing session do not exist there. Dot-source yourMyCmdletscript in the scriptblock forStart-Job
– TheIncorrigible1
Nov 22 '18 at 0:19
I had actually tried that and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access to the file MyCmdlet.ps1!
– ThisRestlessPilgrim
Nov 22 '18 at 0:28
You might be able to use-InitializationScript- I'm unsure what context that gets run in.
– TheIncorrigible1
Nov 22 '18 at 0:29
add a comment |
2
The*-Jobcmdlets start a new runspace so things you load in your existing session do not exist there. Dot-source yourMyCmdletscript in the scriptblock forStart-Job
– TheIncorrigible1
Nov 22 '18 at 0:19
I had actually tried that and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access to the file MyCmdlet.ps1!
– ThisRestlessPilgrim
Nov 22 '18 at 0:28
You might be able to use-InitializationScript- I'm unsure what context that gets run in.
– TheIncorrigible1
Nov 22 '18 at 0:29
2
2
The
*-Job cmdlets start a new runspace so things you load in your existing session do not exist there. Dot-source your MyCmdlet script in the scriptblock for Start-Job– TheIncorrigible1
Nov 22 '18 at 0:19
The
*-Job cmdlets start a new runspace so things you load in your existing session do not exist there. Dot-source your MyCmdlet script in the scriptblock for Start-Job– TheIncorrigible1
Nov 22 '18 at 0:19
I had actually tried that and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access to the file MyCmdlet.ps1!
– ThisRestlessPilgrim
Nov 22 '18 at 0:28
I had actually tried that and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access to the file MyCmdlet.ps1!
– ThisRestlessPilgrim
Nov 22 '18 at 0:28
You might be able to use
-InitializationScript - I'm unsure what context that gets run in.– TheIncorrigible1
Nov 22 '18 at 0:29
You might be able to use
-InitializationScript - I'm unsure what context that gets run in.– TheIncorrigible1
Nov 22 '18 at 0:29
add a comment |
1 Answer
1
active
oldest
votes
My problems were two-fold. As TheIncorrigible1 pointed out, I needed to put the dot-sourcing inside the ScriptBlock. However, I had tried that previously and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access privileges to the file MyCmdlet.ps1!
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
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%2f53422200%2finvoking-custom-cmdlet-from-script-block-in-powershell%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
My problems were two-fold. As TheIncorrigible1 pointed out, I needed to put the dot-sourcing inside the ScriptBlock. However, I had tried that previously and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access privileges to the file MyCmdlet.ps1!
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
add a comment |
My problems were two-fold. As TheIncorrigible1 pointed out, I needed to put the dot-sourcing inside the ScriptBlock. However, I had tried that previously and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access privileges to the file MyCmdlet.ps1!
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
add a comment |
My problems were two-fold. As TheIncorrigible1 pointed out, I needed to put the dot-sourcing inside the ScriptBlock. However, I had tried that previously and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access privileges to the file MyCmdlet.ps1!
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
My problems were two-fold. As TheIncorrigible1 pointed out, I needed to put the dot-sourcing inside the ScriptBlock. However, I had tried that previously and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access privileges to the file MyCmdlet.ps1!
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
answered Nov 22 '18 at 0:30
ThisRestlessPilgrimThisRestlessPilgrim
86112
86112
add a comment |
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%2f53422200%2finvoking-custom-cmdlet-from-script-block-in-powershell%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
2
The
*-Jobcmdlets start a new runspace so things you load in your existing session do not exist there. Dot-source yourMyCmdletscript in the scriptblock forStart-Job– TheIncorrigible1
Nov 22 '18 at 0:19
I had actually tried that and it didn't work. I now realize that's because the credentials I was using in $specialCredentials didn't have access to the file MyCmdlet.ps1!
– ThisRestlessPilgrim
Nov 22 '18 at 0:28
You might be able to use
-InitializationScript- I'm unsure what context that gets run in.– TheIncorrigible1
Nov 22 '18 at 0:29