How can I use PowerShell with the Visual Studio Command Prompt?

by

Stealing liberally from blog post Replace Visual Studio Command Prompt with PowerShell, I was able to get this to work. I added the following to my profile.ps1 file and all is well with the world.

pushd 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC'
cmd /c "vcvarsall.bat&set" |
foreach {
  if ($_ -match "=") {
    $v = $_.split("="); set-item -force -path "ENV:\$($v[0])"  -value "$($v[1])"
  }
}
popd
write-host "`nVisual Studio 2010 Command Prompt variables set." -ForegroundColor Yellow

This has worked well for years – until Visual Studio 2015. vcvarsall.bat no longer exists. Instead, you can use the vsvars32.bat file, which is located in the Common7\Tools folder.

pushd 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools'    
cmd /c "vsvars32.bat&set" |
foreach {
  if ($_ -match "=") {
    $v = $_.split("="); set-item -force -path "ENV:\$($v[0])"  -value "$($v[1])"
  }
}
popd
write-host "`nVisual Studio 2015 Command Prompt variables set." -ForegroundColor Yellow

Things have changed yet again for Visual Studio 2017. vsvars32.bat appears to have been dropped in favor of VsDevCmd.bat. The exact path may vary depending on which edition of Visual Studio 2017 you’re using.

pushd "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools"
cmd /c "VsDevCmd.bat&set" |
foreach {
  if ($_ -match "=") {
    $v = $_.split("="); set-item -force -path "ENV:\$($v[0])"  -value "$($v[1])"
  }
}
popd
Write-Host "`nVisual Studio 2017 Command Prompt variables set." -ForegroundColor Yellow

You can also make the split create just two items to avoid breaking values including the equal sign, which is also the separator of the environment variable name and the value:

$v = $_.split("=", 2); set-item -force -path "ENV:\$($v[0])"  -value

Minor Changes for Visual Studio 2022, now that it’s 64-bit.

pushd "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools"
cmd /c "VsDevCmd.bat&set" |
foreach {
  if ($_ -match "=") {
    $v = $_.split("=", 2); set-item -force -path "ENV:\$($v[0])"  -value "$($v[1])" 
  }
}
popd
Write-Host "`nVisual Studio 2022 Command Prompt variables set." -ForegroundColor Yellow

More Related Contents:

  1. Error ‘LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt’ after installing Visual Studio 2012 Release Preview
  2. UTF-8 without BOM
  3. How do you include additional files using VS2010 web deployment packages?
  4. IIS Express Windows Authentication
  5. Cannot import the keyfile ‘blah.pfx’ – error ‘The keyfile may be password protected’
  6. Changes to Access database do not persist when running app in Visual Studio
  7. Targeting .NET Framework 4.5 via Visual Studio 2010
  8. NUnit isn’t running Visual Studio 2010 code
  9. How do I use MSTest without Visual Studio?
  10. No IntelliSense for C++/CLI in Visual Studio 2010?
  11. Restrictions on installing extensions or add-ins in Visual Studio 2010 Express
  12. Cannot connect to any online resource
  13. Can’t run ASP.NET MVC 2 web app on IIS 7.5
  14. How to fix “Root element is missing.” when doing a Visual Studio (VS) Build?
  15. Using CustomParameter with Visual Studio Multi-Project Template
  16. This project references NuGet package(s) that are missing on this computer
  17. Mercurial .hgignore for Visual Studio 2010 projects
  18. VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed
  19. MSBuild in TeamCity of Visual Studio 2012 solution
  20. After Publish event in Visual Studio
  21. How to make a tabbed window as in the picture using Visual C# (Studio 2010)
  22. I upgraded C++ projects from Visual Studio 2010 to 2015 still its showing Visual Studio (2010)
  23. Running two projects at once in Visual Studio
  24. M_PI works with math.h but not with cmath in Visual Studio
  25. Localhost not working in chrome and firefox
  26. How to set SGEN toolpath in Msbuild to target 3.5 framework
  27. Static library debug symbols
  28. Visual Studio always selects the wrong xsd for App.config
  29. The type or namespace name ‘DbContext’ could not be found [closed]
  30. Visual Studio 2010 related file nesting

Leave a Comment