Storing Resilient Args in Registry for Windows Service Generation #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Storing arguments passed into the
--res-circuits-args
option for commandresilient-circuits.exe service ... install
in the Windows registry.This post gave me the insight on how to do this.
Motivation and Context
Allows arguments to be passed to resilient circuits when it's being ran as a windows service - e.g. you can run the service with a custom app.config location.
Was looking into this because we have a couple of integrations running on a Windows server that we want running in virtual environments / their own integration server.
How Has This Been Tested?
I have generated windows services via command
resilient-circuits.exe service --res-circuits-args "--config-file C:\\Users\\USER\\Path\\To\\app.config" install
and have verified the proper app.config file was loaded by the resilient circuits started through a Windows ServiceChecklist:
Signed-off-by: Liam Mahoney