HOME doesn't appear to be set in PowerShell install script
I'm trying to use a block of powershell for my install script,
and the environment variable $env:Home appears to be
unset. Here is the console output of my build demonstrating the
problem:
-
qwer.png
126 KB
qwer.png
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 17 Jun, 2015 04:23 PM
You can set it by your own?
- Feodor
2 Posted by aggieben on 17 Jun, 2015 04:24 PM
I can try, but what value would I use? In other words, how can I make sure that if something changes on one of the build workers that my build doesn't break?
3 Posted by aggieben on 17 Jun, 2015 04:44 PM
It occurred to me that the dnvm script itself was somehow finding the home directory, so I looked and it's actually using
$env:USERPROFILE, so I did that too and it seemed to work.Support Staff 4 Posted by Feodor Fitsner on 17 Jun, 2015 04:46 PM
Yes, I've been about to write the same that in case of
HOMEit could be safely set toUSERPROFILE.Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.