You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result of upgrading from Chocolatey (was had a default installation path of c:\chocolatey) to new Chocolatey, the underlying Environment Variable for ChocolateyInstall has been changed. However, if you have a previous installation of ChocolateyGUI, it's internal User Setting will still be c:\chocolatey, which means that you will be met with this:
Which I don't think is a great user experience.
@RichiCoder1 what was the thought behind storing this value locally? Why can't we just use the environment variable, or the PATH variable that you are checking for here:
Why store it locally? This seems to limit options when these external settings are changed.
Thoughts?
The text was updated successfully, but these errors were encountered:
- For chocolateyInstall, this has been replaced with a
ChocolateyConfigurationProvider class, instantiated through IoC, that
can provide this information as/when required
- Which at the minute, only provide the ChocolateyInstall property,
however, it could be extended to include other ChocolateyConfiguration
properties, as/when required.
- For chocolateyInstall, this has been replaced with a
ChocolateyConfigurationProvider class, instantiated through IoC, that
can provide this information as/when required
RichiCoder1
pushed a commit
to RichiCoder1/ChocolateyGUI
that referenced
this issue
Jun 29, 2015
- Which at the minute, only provide the ChocolateyInstall property,
however, it could be extended to include other ChocolateyConfiguration
properties, as/when required.
gep13
changed the title
Can't run ChocolateyGUI if "old" User Setting is in place
Can't run Chocolatey GUI if "old" User Setting is in place
Sep 21, 2017
As a result of upgrading from Chocolatey (was had a default installation path of c:\chocolatey) to new Chocolatey, the underlying Environment Variable for ChocolateyInstall has been changed. However, if you have a previous installation of ChocolateyGUI, it's internal User Setting will still be c:\chocolatey, which means that you will be met with this:
Which I don't think is a great user experience.
@RichiCoder1 what was the thought behind storing this value locally? Why can't we just use the environment variable, or the PATH variable that you are checking for here:
Why store it locally? This seems to limit options when these external settings are changed.
Thoughts?
The text was updated successfully, but these errors were encountered: