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.

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

Add check for useBackgroundService #371

Closed
gep13 opened this issue Jan 8, 2017 · 3 comments
Closed

Add check for useBackgroundService #371

gep13 opened this issue Jan 8, 2017 · 3 comments
Assignees
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Jan 8, 2017

ChocolateyGUI needs to look in the config file and see if features/useBackgroundService is there and if it is set to true.

Then allow running install/upgrade without trying to seek admin rights.

@gep13 gep13 added the Feature Issues that introduce new functionality to the project, instead of updating existing functionality label Jan 8, 2017
@gep13 gep13 added this to the 0.15.0 milestone Jan 8, 2017
@ferventcoder
Copy link
Member

Thanks!

@ferventcoder
Copy link
Member

cc @RichiCoder1 (I believe we chatted about this awhile back so if this is already done... ;))

@RichiCoder1
Copy link
Contributor

RichiCoder1 commented Jan 8, 2017

@ferventcoder Saaaadly no. Everything is in place to make this check, but I haven't done the work itself. My actual job went from 1 to 60 just recently.

ferventcoder pushed a commit to ferventcoder/ChocolateyGUI that referenced this issue Jun 12, 2017
When using self-service installs, a feature in Chocolatey for Business,
it provides a background agent that actually performs the
installations. Chocolatey itself handles passing through the proper
information to the background service so that installations can occur.
The GUI should notice the feature is switched on and adjust to allow
non-administrators to run certain commands in the GUI without
attempting to elevate.

Original commit from @RichiCoder1.
ferventcoder added a commit to ferventcoder/ChocolateyGUI that referenced this issue Jun 12, 2017
When calling into chocolatey.lib, if the Container is accessed
prior to having the configuration all set, any additonal components
that Chocolatey attempts to register will be ignored. This causes
issues with using Chocolatey and registering licensed configuration
and components. Ensure that Chocolatey does get set appropriately
by making a call to do that early in the process load.
ferventcoder added a commit to ferventcoder/ChocolateyGUI that referenced this issue Jun 12, 2017
When calling into chocolatey.lib, if the Container is accessed
prior to having the configuration all set, any additonal components
that Chocolatey attempts to register will be ignored. This causes
issues with using Chocolatey and registering licensed configuration
and components. Ensure that Chocolatey does get set appropriately
by making a call to do that early in the process load.
ferventcoder pushed a commit to ferventcoder/ChocolateyGUI that referenced this issue Jun 26, 2017
When using self-service installs, a feature in Chocolatey for Business,
it provides a background agent that actually performs the
installations. Chocolatey itself handles passing through the proper
information to the background service so that installations can occur.
The GUI should notice the feature is switched on and adjust to allow
non-administrators to run certain commands in the GUI without
attempting to elevate.

Original commit from @RichiCoder1.
ferventcoder added a commit to ferventcoder/ChocolateyGUI that referenced this issue Jun 26, 2017
When calling into chocolatey.lib, if the Container is accessed
prior to having the configuration all set, any additonal components
that Chocolatey attempts to register will be ignored. This causes
issues with using Chocolatey and registering licensed configuration
and components. Ensure that Chocolatey does get set appropriately
by making a call to do that early in the process load.
mwallner pushed a commit that referenced this issue Jun 29, 2017
* (GH-371) Enable self-service mode

When using self-service installs, a feature in Chocolatey for Business,
it provides a background agent that actually performs the
installations. Chocolatey itself handles passing through the proper
information to the background service so that installations can occur.
The GUI should notice the feature is switched on and adjust to allow
non-administrators to run certain commands in the GUI without
attempting to elevate.

Original commit from @RichiCoder1.

* (maint) capture connection closed error

There are errors where a connection was closed during an operation,
like when the application is being closed when running a query. Capture
those and allow the application to exit peacefully.

Original commit from @RichiCoder1.

* (maint) Add Pin for German resources

* (GH-425) New source settings

- Added necessary UI elements
- Updated model classes with new properties

* (GH-371) Ensure config is properly set

When calling into chocolatey.lib, if the Container is accessed
prior to having the configuration all set, any additonal components
that Chocolatey attempts to register will be ignored. This causes
issues with using Chocolatey and registering licensed configuration
and components. Ensure that Chocolatey does get set appropriately
by making a call to do that early in the process load.

* (maint) upgrade to Chocolatey 0.10.7

* Ensure we don't elevate when operating through a background agent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants