adding-options-settings

To add a Tools > Options settings page to a Visual Studio extension, you define the settings class, register the option page, and wire up read/write persistence using your chosen extensibility model like VisualStudio.Extensibility, VSIX Toolkit, or VSSDK.

The difference between implementing settings in VisualStudio.Extensibility and VSSDK lies in the architecture: VisualStudio.Extensibility supports out-of-process extensions, while VSSDK is the legacy in-process model, requiring different persistence and change handling patterns provided by this guidance.

To persist user settings and handle change notifications in a VSIX extension, you follow the recommended patterns for reading and writing values, wiring up event listeners to update the UI immediately when a user modifies an option on the settings page.

Yes, you can migrate existing Visual Studio extension settings from VSSDK to the VSIX Community Toolkit by following the cross-model migration steps provided, ensuring persistence and UI consistency are maintained during the transition.

The VSIX Community Toolkit supports roaming profiles for extension settings by utilizing the provided persistence patterns, allowing your saved options to sync across user environments and machines.

Visual Studio extension settings fail to save when the options page closes if the write persistence logic is missing or incorrectly wired, requiring you to implement the proper save patterns outlined for your specific extensibility model.