Reputation: 350
We have a VB.Net CLR 4.0 application in Windows 7 that when you click a button, a webbrowser control pops up and displays a web page. The browser control defaults to IE7 mode, and we need at least IE8 for the page to display correctly (it's an external site that we don't have any control over).
All of our users are on Windows 7 x86 machines, with the following registry key installed through AppSense:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]
"AppName.exe"=dword:00001f40
This works for a majority of our users, but for about 10%, the key just gets completely ignored for some reason, and IE7 mode is used in the control. I have verified that the key is in place on their machines, and that the name matches the executable name in Task Manager, and I have checked their IE9 browsers for any special compatability settings that may have been set in there that would override what is in my key, but I can't find anything out of the ordinary.
Is there any reasonable case that would cause the webbrowser control to completely ignore this key in the registry?
Upvotes: 3
Views: 1385
Reputation: 61666
Use HKEY_CURRENT_USER
instead of HKEY_LOCAL_MACHINE
(i.e.,
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
). That doesn't require admin rights, and you should be setting up this key during runtime, from the app itself. More info, including sample code.
Upvotes: 3