Note that there are some explanatory texts on larger screens.

plurals
  1. POwebbrowser using ie10 c# winform
    primarykey
    data
    text
    <p>I want to force the webbrowser to use IE10 in my c# winform application. I know there are other questions like this but i've already read a lot of them and i don't know where i'm wrong.</p> <p>This is my code:</p> <pre><code>RegistryKey registrybrowser = Registry.LocalMachine.OpenSubKey (@"SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION", true); registrybrowser.SetValue("myAppName", 0x02710, RegistryValueKind.DWord); //Even with QWord </code></pre> <p>I've tried different ways to set the value like: </p> <pre><code>registrybrowser.SetValue("myAppName", 1000, RegistryValueKind.DWord); //Even with QWord and String registrybrowser.SetValue("myAppName", 1000); //even with 0x02710 </code></pre> <p>I write it in the costructor of my main project before InitializeComponent(). I've got Admin permission set in the .manifest file</p> <p>Thanks to all, BlackShawarna</p> <p>EDIT: I discovered that the RegistryKey.SetValue(...); created a key in another path:</p> <pre><code>(@"SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION") </code></pre> <p>even if my instruction said: <code>Registry.LocalMachine.OpenSubKey (@"SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION", true);</code></p> <p>I think it happens because IE10 works on 32bit mode. However I don't understand why it writes in that path even if i specified another one and, above all, why my application doesn't work even if I open Registry.LocalMachine.OpenSubKey(@"Software\Wow6432Node....");</p> <p>If I run my program only in x64 mode, going to properties/build/x64, it won't write the key in my original path.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload