Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update environment for scripts after setting environment variables #729

Closed
ferventcoder opened this issue May 9, 2016 · 1 comment
Closed

Update environment for scripts after setting environment variables #729

ferventcoder opened this issue May 9, 2016 · 1 comment
Assignees
@ferventcoder
Labels
5 - Released Improvement
Milestone
0.9.10

Comments

@ferventcoder
Copy link
Member

When setting environment variables, it would be nice if those variables could be returned as part of the current environment for immediate use in the currently running PowerShell script.
@ferventcoder ferventcoder self-assigned this May 9, 2016
@ferventcoder ferventcoder added this to the 0.9.10 milestone May 9, 2016
@ferventcoder ferventcoder changed the title Update environment after setting environment variables Update environment for scripts after setting environment variables May 9, 2016
ferventcoder added a commit that referenced this issue May 9, 2016
@ferventcoder
(GH-729) Update env after setting env vars for scripts
0fdfd4d 
When setting environment variables, update the session's environment
variables so that those variables can be used immediately in the
currently running PowerShell script.
ferventcoder added a commit that referenced this issue May 9, 2016
@ferventcoder
Merge branch 'stable'
56acefa 
* stable:
  (doc) update CHANGELOG/nuspec
  (GH-728) Fix: Env var changes may require reboot
  (GH-729) Update env after setting env vars for scripts
  (GH-723) Warn when can't find file
  (GH-723) Convert msiexec to full path
  (GH-723) Ensure wusa.exe uses a full path
  (GH-727) Fix: Name is bad if response has params
@ferventcoder
Copy link
Member Author

This has been released in https://chocolatey.org/packages/chocolatey/0.9.10-beta-20160509

You can upgrade to it with choco upgrade chocolatey --version 0.9.10-beta-20160509 or after another hour or so you can use choco upgrade chocolatey -pre.

TheBigBear pushed a commit to TheBigBear/choco that referenced this issue May 14, 2016
@ferventcoder @TheBigBear
(chocolateyGH-729) Update env after setting env vars for scripts
96335ae 
When setting environment variables, update the session's environment
variables so that those variables can be used immediately in the
currently running PowerShell script.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Improvement
Projects
None yet
Milestone
0.9.10
Development

No branches or pull requests
2 participants
@ferventcoder @gep13