settings.json for a development team

[alanseiden]

A client asked us if it would be practical for his desktop support team to install a specially customized settings.json file for all team members. This idea would help him to set a consistent set of "Protected paths" for everyone. This idea sounded practical to me, but is there any reason not do to it, why it wouldn't work? Or any helpful hints or tips?

[sebjulliand]

That reminds me of this draft: #2341
It would be an even better way to achieve this I guess, by having common, shared settings hosted on the IFS. But it's still a draft 😅

The problem with handing over a settings.json file is that it's not only for Code for i, but for VS Code entirely. It may be OK in some cases, but not so practical for everyone. This being said, it would be a good starting point when installing VS Code from scratch.

[worksofliam]

@alanseiden You might want to check out this page: https://code.visualstudio.com/docs/setup/enterprise