{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/Home/issues/413","labels_url":"https://api.github.com/repos/aspnet/Home/issues/413/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Home/issues/413/comments","events_url":"https://api.github.com/repos/aspnet/Home/issues/413/events","html_url":"https://github.com/aspnet/Home/issues/413","id":64424103,"number":413,"title":"Install script (falsely) claims to modify process environment","user":{"login":"Jaykul","id":192942,"avatar_url":"https://avatars.githubusercontent.com/u/192942?v=3","gravatar_id":"","url":"https://api.github.com/users/Jaykul","html_url":"https://github.com/Jaykul","followers_url":"https://api.github.com/users/Jaykul/followers","following_url":"https://api.github.com/users/Jaykul/following{/other_user}","gists_url":"https://api.github.com/users/Jaykul/gists{/gist_id}","starred_url":"https://api.github.com/users/Jaykul/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Jaykul/subscriptions","organizations_url":"https://api.github.com/users/Jaykul/orgs","repos_url":"https://api.github.com/users/Jaykul/repos","events_url":"https://api.github.com/users/Jaykul/events{/privacy}","received_events_url":"https://api.github.com/users/Jaykul/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-26T02:44:29Z","updated_at":"2015-03-26T02:44:29Z","closed_at":null,"body":"When running the install script the ```dnvm setup``` command outputs text indicating that it has set the process environment variables so I can use DNVM:\r\n```\r\nAdding C:\\Users\\Jaykul\\.dnx\\bin to Process PATH\r\nAdding C:\\Users\\Jaykul\\.dnx\\bin to User PATH\r\nAdding C:\\Users\\Jaykul\\.dnx to Process DNX_HOME\r\nAdding C:\\Users\\Jaykul\\.dnx to User DNX_HOME\r\n```\r\n\r\nIn fact, after the install finishes, the environment is not set, because the install script is (needlessly) running multiple nested processes.\r\n\r\nIf you just use the PowerShell portion of the install script (the contents of the &{...} block), it *could* work, but it still doesn't, because in the `dnvminstall.ps1` when you call `dnvm setup` you are running the CMD version (starting a new process) which *then* calls the PowerShell version (starting another new process), so when the process environment is set, it's on a process which immediately terminates.\r\n\r\nIf the `dnvminstall.ps1` script just called the `dnvm.ps1` script directly instead, my environment would be set, and I wouldn't need to exit PowerShell and start a new process to pick up the changes to my PATH.\r\n\r\nMy suggestion would be to have the home README specify a PowerShell-friendly version of the install command, and just tell people to run it there -- and **also** alter the `dnvminstall.ps1` script so that you're not calling CMD from PowerShell just to get you back into Powershell...\r\n\r\nThe alternative might be to put a -quiet switch on the setup command so you're not printing messages that aren't true ;-)\r\n\r\n\r\nFWIW, the PowerShell 3+ version of the install command could be as simple as:\r\n```\r\n$Branch='dev'; iex (irm https://github.com/aspnet/Home/raw/dev/dnvminstall.ps1)\r\n```\r\n\r\n"}}