.NET Framework Bookmark and Share   
 index > .NET Base Class Library > Wow6432Node
 

Wow6432Node

Hi

We have code that was written some time back when XP64 was very new, it is code that may find itself running in either 32-bit or 64-bit mode, depending upon the app and OS that loads it.

I am seeing the code explicitly refer to the Wow3264Node section, if it is running as 64-bit, else it just refers to the conventionally named key.

Now it seems that there is no need to do this, code running as 64-bit should be able to refer to the same logical keys as code running as 32-bit and the OS will internally redirect the code to either the 32-bit or 64-bit subtrees.

Our code was coded a long time ago and may well have misunderstood all this.

BUT the code is installed with an MS Setup Project and it seems tha this ONLY creates our keys under Wow3264Node subtree, this may have confused the developers that wrote the original code.

I am expecting that when we run our setup on a 64-bit OS, that it would create the two physcal regsitry subtrees, but it ONLY creates one (under Wow3264Node).

So how do I overcome this, how do we get the setup/installer to create two sets of keys rather than just the one?

Thx
H
Captain Kernel
Sure, your installer no doubt runs in 32-bit mode so it only writes the Wow6432 keys. MSI questions are very off topic here, I suspect you can find the link you need from this blog post.

Hans Passant.
nobugz
Sure, your installer no doubt runs in 32-bit mode so it only writes the Wow6432 keys. MSI questions are very off topic here, I suspect you can find the link you need from this blog post.

Hans Passant.
nobugz

You can use google to search for other answers

Custom Search

More Threads

• Namespace Class Reference (Trying to mimic DLL that is referred to with thisNameSpace.thisClass.1 (if the first part is namespace and the second part is the class, then what is the 1?
• Starting the Windows pause screen
• IIS does not release Excel file created using OLEDB
• Accessing Collection Items
• Timer function with millaseconds elapsed (in dos/command-line)
• Windows Service
• Multi Threading with BinaryWriter
• problems of .NET printing in IE
• assembly for SoapFomatter
• System.Globalization.CultureInfo