current community

your communities

more stack exchange communities

Stack Exchange
tour help
careers 2.0
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 10 down vote favorite
6

I have one big batch script which sets bunch of environment variables. I want to call that batch script from powershell, that way I can get benefits of both i.e. enviorment variable set by my script and powershell.

share|improve this question
add comment

4 Answers

up vote 7 down vote accepted

The idea comes from this blog post: Nothing solves everything – PowerShell and other technologies

Here is my version of this script. It calls a batch file (or any native command) and propagates its environment:

UPDATE: Improved and better tested version of this script is here: Invoke-Environment.ps1

<#
.SYNOPSIS
    Invokes a command and imports its environment variables.

.DESCRIPTION
    It invokes any cmd shell command (normally a configuration batch file) and
    imports its environment variables to the calling process. Command output is
    discarded completely. It fails if the command exit code is not 0. To ignore
    the exit code use the 'call' command.

.EXAMPLE
    # Invokes Config.bat in the current directory or the system path
    Invoke-Environment Config.bat

.EXAMPLE
    # Visual Studio environment: works even if exit code is not 0
    Invoke-Environment 'call "%VS100COMNTOOLS%\vsvars32.bat"'

.EXAMPLE
    # This command fails if vsvars32.bat exit code is not 0
    Invoke-Environment '"%VS100COMNTOOLS%\vsvars32.bat"'
#>

param
(
    [Parameter(Mandatory=$true)] [string]
    # Any cmd shell command, normally a configuration batch file.
    $Command
)

cmd /c "$Command > nul 2>&1 && set" | .{process{
    if ($_ -match '^([^=]+)=(.*)') {
        [System.Environment]::SetEnvironmentVariable($matches[1], $matches[2])
    }
}}

if ($LASTEXITCODE) {
    throw "Command '$Command': exit code: $LASTEXITCODE"
}

P.S. Here is the proposal to add similar capability to PowerShell: Extend dot sourcing concept to cmd files

share|improve this answer
1  
You may want to use just $Command > nul 2>&1 && set just in case $Command has a non-zero exit code but still changes the environment. –  Јοеу Dec 9 '10 at 23:02
add comment
up vote 10 down vote

If you grab the PowerShell Community Extensions, there is an Invoke-BatchFile command in it that runs the batch file but more importantly, it retains any environment variable modifications made by the batch file e.g.:

>Invoke-BatchFile 'C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat'
Setting environment for using Microsoft Visual Studio 2008 x86 tools.
share|improve this answer
    
Pretty cool, I have to look in the src :) –  stej Dec 8 '10 at 17:07
    
Notes to self, as per below, 1.To install from the zip file on codeplex, right-click and a modal button, "unblock" appears; click it. 2.Unzip after unblocking and then place the folder in your modules location, as per $PSHome\Modules. stam.blogs.com/8bits/2010/06/… –  AnneTheAgile Aug 24 '12 at 18:46
add comment
up vote 1 down vote

Is it possible to convert your batch script to PowerShell script? If you run the bat file, its is executed in separate session that doesn't modify PowerShell's env variables.

You can work with env variables very smoothly:

PS> Get-ChildItem env:

Name                           Value
----                           -----
ALLUSERSPROFILE                C:\ProgramData
APPDATA                        C:\Users\xyz\AppData\Roaming
CommonProgramFiles             C:\Program Files (x86)\Common Files
CommonProgramFiles(x86)        C:\Program Files (x86)\Common Files
CommonProgramW6432             C:\Program Files\Common Files
COMPUTERNAME                   xyz
ComSpec                        C:\Windows\system32\cmd.exe
DXSDK_DIR                      D:\prgs\dev\Microsoft DirectX SDK (August 2009)\
FP_NO_HOST_CHECK               NO
HOMEDRIVE                      Z:
HOMEPATH                       \
...

PS> Get-Item env:path
Name  Value
----  -----
Path  c:\dev\CollabNet\SubversionClient;C:\Windows\system32;...

Or even (much shorter, returns only string):

PS> $env:path
c:\dev\CollabNet\Subversion Client;C:\Windows\system32;...

You can change the environment path like this:

PS> $env:path += ";c:\mydir"

And you can even set environment variables at machine level like this:

# fist arg = env variable name, second = value, third = level, available are 'Process', 'User', 'Machine'
PS> [Environment]::SetEnvironmentVariable('test', 'value', 'machine')
share|improve this answer
add comment
up vote 0 down vote

You can run a batch script from Powershell just by putting its name, but that won't help you. Environment variables set in the batch script will only be visible from that batch and anything that batch runs. Once the control returns back to Powershell the environment variables are gone. You could have the batch script run set at the end and then parse its output into your PSH environment variables, though.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.