Registry Settings Management in Deployment
The Registry Editor allows you to specify registry keys and values to be added to the registry of the target computer.
By default the Registry Editor displays a standard set of registry keys that correspond with the standard Windows registry keys: HKEY_CLASSES_ROOT, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, HKEY_USERS, and HKEY_PER_USER. For Setup projects, additional keys that match the Manufacturer property for the project are displayed under HKEY_CURRENT_USER\Software and HKEY_LOCAL_MACHINE\Software.
You can add your own keys under any registry key or sub-key; add string, binary, or DWORD values to any key; or import registry files.
Most items in the Registry Editor, including keys and values, can be moved between nodes by dragging with the mouse or by using the Cut and Paste commands on the Edit menu.
The following topics describe tasks that can be accomplished in the Registry Editor.
|
Topic |
Description |
|---|---|
|
Explains how to specify registry keys for a target computer. |
|
|
How to: Add and Delete Registry Values in the Registry Editor |
Describes how to specify values for registry keys on a target computer. |
|
Explains how to specify a default registry value for a key on a target computer. |
|
|
Explains how to import an existing registry file. |
|
Topic |
Description |
|---|---|
|
Describes properties available in the Registry Editor. |
|
|
Explains how to open the deployment editors. |
|
|
Describes the File System Editor, which allows you to add project outputs, files, and other items to a deployment project and specify where they will be installed on the target computer. |
|
|
Describes the File Types Editor, which is used to establish file associations on the target computer. |
|
|
Describes the User Interface Editor, which can be used to specify and set properties for predefined dialog boxes that are displayed during installation on the target computer. |
|
|
Describes the Custom Actions Editor, which allows you to specify additional actions to be performed on the target computer at the end of an installation. |
|
|
Describes the Launch Conditions Editor, which allows you to specify conditions that must be met in order to successfully run an installation. |
|
|
Describes new features related to setup and deployment. |
StevenPo (MSFT) replies:
The product teams don't really monitor the documentation for feedback. To provide them actionable feedback about the product and features, you can submit a request by using Connect (http://connect.microsoft.com/visualstudio ). You might also want to post in one of the MSDN forums and ask other users to vote for your suggestion as the product teams typically focus on items that have heavy customer support. Your suggestion seems to make sense to me, and I don't know why Copy is not supported.
Go to regedit and setup the values you want to copy. Do an Export from the Registry to create an export file. Edit the file you just created (Notepad, etc), use copy/paste to add the new keys/values you wish to setup in the Deployment Project.
Now right-click the Deployment Project in Visual Studio, select 'View Registry'. Now select 'Registry on Target Machine', then go to Action in the menu bar, and choose Import. In the dialog box that appears, select the Registry Export file you edited. The settings will now be added to your Deployment Project, saving you a lot of work.
- 1/3/2011
- joopdev
- 1/3/2011
- joopdev
