Assembly: Microsoft.VisualStudio.Shell (in microsoft.visualstudio.shell.dll)
Classes implementing IProfileManager, must also implement, which can be done by deriving the class from .
Providing Visual Studio settings support for a VSPackage should be done by implementing IProfileManager on a class independent of the class implementing the VSPackage itself.
This is because a class providing IProfileManager support will be instantiated when a user chooses the Import/Export Settings command on the Tools menu to save or retrieve Visual Studio state.
The Component base class does this for the derived class and it is the easiest way to fulfill the requirement.
The object implementing IProfileManager is registered as supporting a given VSPackage by applying ato the package implementation. For more information, see and ProvideProfileAttribute.
Implementand to use the and interfaces to save VSPackage state to on-disk Visual Studio settings storage.
Implementand to save information to local storage (typically the registry), and that VSPackage.
The Visual Studio environment first calls LoadSettingsFromStorage and then SaveSettingsToXml for settings export operations.
LoadSettingsFromXml and then SaveSettingsToStorage are called for settings import operations.
For more information, seeand .
The Visual Studio also calls LoadSettingsFromStorage when it starts up a VSPackage to properly initialize its state.Notes to Implementers Implement this interface on a class when a VSPackage needs to save or retrieve settings from disk via the Visual Studio settings mechanism, as well as keeping its state synchronized with local storage (such as the registry). Classed implementing IProfileManager, must also implement IComponent.
TasksHow to: Export Settings by Using the Managed Package Framework
How to: Import Settings by Using the Managed Package Framework