Fetch User EnvironmentThis extension checks that the development environment has the required settings applied and extensions installed, as determined by a development leader. Local user settings and installed extensions are compared with those stored at a shared location. User settings that are incorrect are updated and user settings that are missing are merged, all other settings are unchanged. Default settings can also be applied if the user has not previously specified them. Extensions that are missing or old are side loaded to allow for management of proprietary extensions that are not available in the marketplace, all other extensions are unchanged. Features
UsageOnce configured (see below), upon starting Visual Studio Code this extension will automatically check that all required settings have been applied and that all required extensions have been installed. The extension can also be run manually through the command palette. To compare the current user settings with those at the shared location, open the command palette and run the following command. Settings that are incorrect or missing will be updated. This command will also apply any default settings that have not yet been specified by the user.
To compare extensions that are installed locally with those at the shared location, open the command palette and run the following command. Extensions that are newer or missing will be side loaded.
ConfigurationThis extension requires that the shared locations to retrieve the settings and extensions are specified. A prompt requesting the paths to the shared locations will be displayed upon the first manual use from the command palette. The paths can also be updated manually. For example on a Windows system with a shared network resource mapped to Z drive the configuration may look as follows:
Initial PreparationBefore this extension can compare and retrieve settings and extensions, the content at the shared locations must first be created. This can be done via the command palette or manually. Command paletteCreating the content via the command palette will simply duplicate the current user environment to the shared locations that have been specified. NOTE: To prevent an accidental overwrite of the content, the shared locations must be empty. The operation will be terminated otherwise. The command palette item to create the shared content is disabled by default. To enable it change the following setting:
Once the current user environment is configured correctly, and the command palette item is enabled, open the command palette and run the following command:
ManualManual creation of the content is merely a task of copying the desired settings and extensions to the shared locations. Once the user environment is configured correctly, copy the settings and extensions from the following locations: Settings
Extensions
Default SettingsThe file containing the default settings must be created manually and be stored in the shared location for the settings. To allow for different default settings for different development teams or users, the filename for the default settings file can be configured. Leaving the filename as null will disable this feature. The default settings file must be in JSON format. For example, the configuration for the default settings file may look as follows:
Available CommandsThe following commands are available on the command palette:
SettingsAll settings and default values are below. See above for usage details.
Release NotesSee CHANGELOG.md |