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
Implement custom settings through env params for NAV and Clients #125
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forgot to handle non-existent JSON settings as well
SetupClickOnce exists in all version folders, you have only modified the one in 100. |
Yes, I wanted to get your feedback before copying to all folders. SetupWebClient vs. SetupWebConfiguration: As it is the same in all releases I thought it might make sense to put it in the central one instead of copying. But I'll move it. 2017 is the only release where we need to support web.config and navsettings.json, right? 2013 to 2016 is web.config only and 2018 navsettings.json only? |
Thanks |
ok, moved the parts around |
Merged, thanks Tobias |
What would be the format to pass these customsettings via the additionalParameters?
|
Use new-navcontainer instead of new-csidedevcontainer. |
This addition allows to set customNavSettings, customWinSettings and customWebSettings to set arbitray config settings for the NAV server instance, ClickOnce Windows Client and WebClient. The format is:
<variablename>="<key1>=<value1>,<key2>=<value2>"
e.g.
customNavSettings="EnableDebbuging=true,ReportPDFFontEmbedding=false"
In cases where the config setting doesn't exist, the script creates it. Setting or creating a config value is also shown in the log
Tested with 2017-cu5-de and 2018-rtm-de