Platform target x86 and Any CPU

Question

I have small problem with simple code. This code is working properly on "x86" mode but not on "Any CPU" mode, maybe it is possible to run one class on "x86" and another class on "Any CPU" mode? Code:

namespace Software_Info_v1._0
{
using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Win32;

public class Adobe
{
    public string GetAdobeVersion()
    {
        try
        {
            RegistryKey adobe = Registry.LocalMachine.OpenSubKey("Software").OpenSubKey("Adobe");
            if (adobe != null)
            {
                RegistryKey acroRead = adobe.OpenSubKey("Acrobat Reader");
                if (acroRead != null)
                {
                    string[] acroReadVersions = acroRead.GetSubKeyNames();
                    foreach (string versionNumber in acroReadVersions)
                    {
                        Console.WriteLine("Acrobat Reader version: " + versionNumber);
                    }
                }
            }
        }
        catch
        {
        }
        return null;
    }
}
}

You need to specify exactly what is "not working" in order for people to help you. — adelphus, Feb 21 '12 at 14:41
@jpsstavares This is a 64 bit machine as otherwise the "Any CPU" target would behave in the same way as the "x86" target — Justin, Feb 21 '12 at 14:47
this code in "x86" mode is able to read adobe reader version from register, but I have more code in my program witch one must work in "any CPU" mode. So if I change mode to "Any CPU" then I can't get adobe reader version in my console screen — zee, Feb 21 '12 at 14:48

score 7 · Accepted Answer · edited May 23 '17 at 11:47

This is because of registry redirection.

The structure of the registry is different for 32-bit and 64-bit OS.

See this MSDN article for more information.
See also this SO thread.

Assuming you are running your application on a 64-bit machine, compiling for x86 target makes your program run using WOW64 mode (32-bit process on 64-bit) and you're reading keys under the Wow6432Node. See Weird behaviour when reading registry in C#

score 1 · Answer 2 · answered Feb 21 '12 at 14:43

When running as 32bit, the registry key gets redirected. When you run as 64bit, it won't get redirected, and thus won't hit the key to which adobe's registry entry got redirected anymore.

So I'd create a Find32BitRegEntry(string path) function, that does nothing on 32bit, and adds the redirect on x64.

score 0 · Answer 3 · edited May 23 '17 at 10:34

0

The registry keys can be in a different place on 64 bit machines - see this. (Notice that RegistryKey in your sample code comes from Microsoft.Win32 ?)

I think you need to use a Registry Redirector, there's some talk about it over here.

edited May 23 '17 at 10:34

Community

1
1

answered Feb 21 '12 at 14:49

Bridge

29,818
9
60
82

Platform target x86 and Any CPU

3 Answers3