🚀 go-pugleaf

"Peter" <Will_Bounce_So_Use_My_First_Name@Smart-Projects.net> wrote in
message news:45411265$1@newsgroups.borland.com...

> All my in-app registry handling (settings etc.)(also in combination with
the
> installer (Inno)) happens in:
> HKEY_CURRENT_USER\Software
> Does this key map into one of the reflected keys ?

HKEY_CURRENT_USER maps to HKEY_USERS\{current user SID}.  Whether that is
actually refected or not, I'm not sure.  The documentation is a little
ambiquious about that.  It suggests that it is not, but I have seen people
say that it is.  You will just have to use RegQueryReflectionKey() to find
out if a given key is reflected or not in your code, so that you can then
adjust your reading/writing accordingly as needed.  Microsoft recommends
that anyway.  Unfortunately, I have also seen Microsoft state in online
messages that "[RegQueryReflectionKey] simply says if someone set disable
reflection on the key. Reflection is enabled doesn't mean it will be
reflected."  So it seems that only certain pre-defined keys may actually
take part in reflection.

> So can I conclude that for my own application registry handling I
> am working solely in the 32 bit view ?

Only if your application is compiled for 32-bit.  64-bit applications will
access the 64-bit section of the Registry instead.

> And should I build a 64bit version, I would not have the benefit
> of mirroring for those keys then ?

The 32-bit and 64-bit versions of your application would maintain separate
copies of the key data.  To force a 32-bit or 64-bit application access the
64-bit portion of the Registry specifically, you have to specify the
KEY_WOW64_64KEY flag when opening/creating/deleting a key.  Likewise, to
force the 32-bit portion, use the KEY_WOW64_32KEY flag.

I don't know if you can create reflection for your own keys or not.  The
documentation for the RegEnableReflectionKey() and RegDisableReflectionKey()
suggests that they only work for keys that are pre-defined for reflection.


Gambit