-
Notifications
You must be signed in to change notification settings - Fork 255
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.
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
Remembered arguments are pulled from system Chocolatey install when debugging #980
Closed
4 tasks done
Labels
5 - Released
The issue has been resolved, and released to the public for consumption
NO RELEASE NOTES
Should not be included in the release notes - not enhancing or fixing end product
Milestone
Comments
TheCakeIsNaOH
added a commit
to TheCakeIsNaOH/ChocolateyGUI
that referenced
this issue
Jan 28, 2023
… install location This sets the Chocolatey install directory to the current assembly directory when built as a debug build. This allows correctly getting the location of remembered arguments from the debug installed package(s) instead of from the systemwide install of Chocolatey. If a debug build is in use, then ChocolateyGUI is using the chocolatey lib assembly, so true can be returned in all cases.
10 tasks
gep13
pushed a commit
to TheCakeIsNaOH/ChocolateyGUI
that referenced
this issue
Jun 9, 2023
This sets the Chocolatey install directory to the current assembly directory when built as a debug build. This allows correctly getting the location of remembered arguments from the debug installed package(s) instead of from the systemwide install of Chocolatey. If a debug build is in use, then Chocolatey GUI is using the chocolatey lib assembly, so true can be returned in all cases.
gep13
pushed a commit
to TheCakeIsNaOH/ChocolateyGUI
that referenced
this issue
Jun 9, 2023
This sets the Chocolatey install directory to the current assembly directory when built as a debug build. This allows correctly getting the location of remembered arguments from the debug installed package(s) instead of from the systemwide install of Chocolatey. If a debug build is in use, then Chocolatey GUI is using the chocolatey lib assembly, so true can be returned in all cases.
gep13
added a commit
that referenced
this issue
Jun 9, 2023
…cation (#980) When using debug install, use assembly directory for install location
gep13
added a commit
that referenced
this issue
Jun 29, 2023
* release/2.1.0: (maint) Update to latest version of chocolatey.lib (maint) Update GRM configuration file (maint) Remove version bump in nuspec file (build) Use latest Chocolatey.Cake.Recipe package (maint) Switch to Http for variable names (#1014) Add advanced option to ignore cached items (#1014) Ignore cached files on forced outdated check (build) Make build files consistent with others (#993) (fix) Correct syntax in KTS file (#993) Add TC schedule trigger (maint) Fix StyleCop warnings (#980) Use assembly location when debugging (maint) Update to released alpha package (#1003) Handle null keys during source translation (#1005) Normalize version numbers (maint) Add banned api analyzer (maint) Remove usage of obsolete methods (maint) Update to latest Chocolatey.Lib package
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
5 - Released
The issue has been resolved, and released to the public for consumption
NO RELEASE NOTES
Should not be included in the release notes - not enhancing or fixing end product
Checklist
What You Are Seeing?
When trying to view remembered args for an installed package in debug Chocolatey GUI, it tries to load the remembered args from the system Chocolatey CLI install, instead of from the debug install.
What is Expected?
That it is able to load remembered args when debugging.
How Did You Get This To Happen?
System Details
Installed Packages
Output Log
Additional Context
N/A
The text was updated successfully, but these errors were encountered: