Difference between revisions of "RegyRemove"
(→Scan Results: new) |
|||
| Line 24: | Line 24: | ||
# The data to be removed from the term. An [[AlgoPrefix|Algo-Prefix]] is allowed here. {{AlgoPrefix}} {{PathTemplates}} | # The data to be removed from the term. An [[AlgoPrefix|Algo-Prefix]] is allowed here. {{AlgoPrefix}} {{PathTemplates}} | ||
# This field supports [[Advanced build parameters|advanced build parameters]]. | # This field supports [[Advanced build parameters|advanced build parameters]]. | ||
| + | |||
| + | ===Scan Results=== | ||
| + | * A special entry that allows removal of parts of data during fixing. | ||
==See also== | ==See also== | ||
Revision as of 13:34, 18 February 2008
Removes data from a registry value.
Usage
RegyRemove:<description>,<rootkey>,<keypath>,<value>,[,advanced build parameters]
Examples
RegyRemove:"Example",HKEY_CURRENT_USER,"\QATests\SBI\RegyRemove\","remove1","silly "
If you start with this registry entry:
[CURRENT_USER\QATests\SBI\RegyRemove\] "remove1"="What a silly example."
You would end with
[CURRENT_USER\QATests\SBI\RegyRemove\] "remove1"="What a example."
Description
This removes partial data from a registry value, keeping the value and the surrounding data intact. This makes sense only for REG_SZ, REG_EXPANDSZ and REG_MULTISZ values.
- First, a description. Using a description template instead of plain text is recommended so that the user will receive a localized version.
- The root key, where HKEY_CURRENT_USER stands for all users actually.
- The path to the value, starting with a backslash. PT
- The name of the value. An Algo-Prefix is allowed here. AP PT
- The data to be removed from the term. An Algo-Prefix is allowed here. AP PT
- This field supports advanced build parameters.
Scan Results
- A special entry that allows removal of parts of data during fixing.
