windows - Is there any reason to not use KEY_WOW64_64KEY? -


according microsoft key_wow64_64key , key_wow64_32key forces application operate on 64-bit or 32-bit registry, respectively. there risks using key_wow64_64key? if convert 32-bit application 64-bit in future, can rely on registry keys being in same place if user installs update.

when should use 32-bit registry instead? guess if wanted support installing both 32-bit , 64-bit versions of application side-by-side, wouldn't want that.

there 2 main reasons option:

the first if upgrade application x86 x64; if don't explicitly pass registry in options (which older applications won't), x64 build won't able retrieve registry keys set x86 build.

the second reading information system registry keys. there os information isn't exposed winapi , exists in 1 registry or other.

if you're writing new application, it's not issue; can explicitly use 1 registry or other , not worry.


Comments

Popular posts from this blog

node.js - Mongoose: Cast to ObjectId failed for value on newly created object after setting the value -

gradle error "Cannot convert the provided notation to a File or URI" -

python - NameError: name 'subprocess' is not defined -