[wpkg-users] [OT] Adding a spurious registry value in a key...

[Rainer Meier]

Hi Marco,

On 23.09.2010 11:19, Marco Gaiarin wrote:
> Probably there's no a simple yes/no answer to this question, but...
> 
> Normally in package that mangle registry i use the ''reg'' command and
> i test the values on check conditions.
> 
> But sometimes values are so many that i use regedit /s and a .reg file,
> loosing (roughly) the ability to using check conditions.
> 
> In this package, can i simple add a fake value (WPKGVersion?) on the
> key testing that on check conditions?
> Normally windows programs what do if there's a spurious value? I
> suppose they ignore them, but... i prefer ask here.

Yes, you are right.
Registry values which are not read by any program do not harm others. Just make
sure not to overwrite any value existing.

Typically applications store values at
HKLM\Software\<company>\<application>

(or in HKCU for current user-specific settings)

Also WPKG stores values at
HKLM\Software\WPKG

An easy way not to collide with others is to open your own key. Eg. at
HKLM\Software\Marco-Gaiarin\SettingsVersion
Type: D_WORD
Value: [Version]

Then just insert an updated value in your *.reg file and import it along with
the other settings and let WPKG check for the value. This will make sure your
settings got imported.

Note: You can import only HKLM\* settings using WPKG system service. All HKCU\*
settings will affect only the SYSTEM account and have no effect on other users.


br,
Rainer