Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > Windows Server Forums > Windows PowerShell > Dot-Sourcing a PowerShell script in .NET and then running a cmdlet defined in the script.

Answered Dot-Sourcing a PowerShell script in .NET and then running a cmdlet defined in the script.

    •  
      Thursday, June 25, 2009 6:04 PM
       
        Has Code
      Sign In to Vote
      0
      Sign In to Vote
      The HyperV guys have a nice hyperv.ps1 script that contains definitions for cmdlets like (Get-VM, Get-VMHost etc. etc.).

      So in the PowerShell command line i dot source (. ./hyperv.ps1) then run 'Get-VM' and all is well.

      I'd like to do the same from .Net:

      string scriptContents = string.Empty;
using(StreamReader fs = new StreamReader(@"hyperv.ps1"))
{
  scriptContents = fs.ReadToEnd();
}
.
.
.
.
pipeline.Commands.AddScript("scriptContents");
pipeline.Command.Add(new Command("Get-VM"));
pipeline.Invoke();
      Unfortunately I get a CommandNOtFoundException :"The term 'Get-VMHost' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again." 

      Thanks for your help in advance.

      Matt




       

    Answers

    • Friday, June 26, 2009 7:10 PM
      Moderator
       
       Answered
      Sign In to Vote
      2
      Sign In to Vote
      If you used IE to download this script, right-click on hyperv.ps1 and select "unblock".  That might be your problem...
       

    All Replies

    • Thursday, June 25, 2009 6:31 PM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      That's a good one.

      Since this is a runspace, I think I'd try this first by modifying the function in hyper.ps1:

      Instead of:
      function get-vm {...
      }

      Change it to:
      function global:get-vm {...
      }

      Then when you load hyper.ps1, I think you will have access to the function in your current scope.

      I don't know what might be the implications of changing *all* the functions to be in the global scope in this case.
       
    • Thursday, June 25, 2009 10:42 PM
       
        Has Code
      Sign In to Vote
      0
      Sign In to Vote
      I figured out that i should be loading the script in the runspace rather than the pipeline: 

      myRunspaceInvoke.Invoke(". ./hyperv.ps1");

      Unfortunately I get a "AuthorizationManager check failed." exception as I believe the script is not signed or some other authentication problem.
       
    • Friday, June 26, 2009 1:38 PM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Are you using the new v2 CTP3 here?

      Known problem:
      https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=466285&SiteID=99
       
    • Friday, June 26, 2009 5:17 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Nope I'm using Powershell 1.0.

      I can't seem to find that feedback item you've linked.

      Can you cut and paste the summary here so I can read it over?
       
    • Friday, June 26, 2009 5:53 PM
      Moderator
       
       Proposed Answer
      Sign In to Vote
      0
      Sign In to Vote
      I'll have to try some more testing with runspaces.  This may be related directly to WMI though...

      When the WMI service (winmgmt) is "paused", the policy execution equal to "AllSigned" and i run powershell.exe, i get this error :
      -------
      Windows PowerShell V2 (Community Technology Preview - Features Subject to Change)
      Copyright (C) 2008 Microsoft Corporation. All rights reserved.

      AuthorizationManager check failed.
      At line:1 char:2
      + . <<<< 'C:\Documents and Settings\UserTest\Mes documents\WindowsPowerShell\profile.ps1'
          + CategoryInfo         : NotSpecified: (:) [], PSSecurityException
          + FullyQualifiedErrorId : RuntimeException

      AuthorizationManager check failed.
      At line:1 char:2
      + . <<<< 'C:\Documents and Settings\UserTest\Mes documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'
          + CategoryInfo         : NotSpecified: (:) [], PSSecurityException
          + FullyQualifiedErrorId : RuntimeException
       
    • Friday, June 26, 2009 6:54 PM
       
        Has Code
      Sign In to Vote
      0
      Sign In to Vote
      Good call, but my service is running so I don't think this is the case for my issue.

      I was thinking that perhaps it is due to the fact that even if you set the execution policy to allow any script to run, you are still prompted to allow a script to run:

      Security Warning
Run only scripts that you trust. While scripts from the Internet can be useful, this script can potentially harm your
computer. Do you want to run C:\hyperv.ps1?
[D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"): r
      Perhaps this is why the AuthorizationManager check fail is being raised as there is no user confirmation when dot-sourcing/running a script from .net.
       
    • Friday, June 26, 2009 7:10 PM
      Moderator
       
       Answered
      Sign In to Vote
      2
      Sign In to Vote
      If you used IE to download this script, right-click on hyperv.ps1 and select "unblock".  That might be your problem...
       
    • Monday, June 29, 2009 7:46 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Yep that got rid of the 'prompt' which made it work ok in .NET.

      Thanks for you help.

      On a side note I went with putting the cmdlet code from the .ps1 file into string resources in my .NET project as I do not want the need for the heightened priviledges required for dot-sourcing a script.
       
    • Friday, October 21, 2011 1:25 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Thank you for this simple yet effective bit of advice. I'm working on a remote system where I have several PowerShell script files that run in a runspace hosted in IIS 7.5. One script sets up the execution environment and then calls another script to do a bunch of work and delegate some re-factored work in the other scripts. Well, the first call worked fine but then the others failed with the highly entertaining "AuthorizationManager check failed" exception. I elevated permissions for the IIS app pool, tried changing NTFS permissions on the script files and then drank a few beers to see if it was better...it wasn't.

      I then decided to approach this fresh after a few days (and possibly more beers!) and found this post. The key is the IE download. I had used IE to pull down a few files over HTTP from our website and guess which files they were. Yep! You betcha...the very files that all failed when the AuthorizationManager calls ran! Needless to say, this is a great piece of info and handy when you're moving files around using a browser.

      Thanks again!