Native calls to IME fail to work in Windows 7 - by Rich Chinnici

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773427 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/4/2012 7:57:46 AM
Access Restriction Public


We have C# code that uses P/Invoke native calls that works perfectly fine in Windows XP to enable the IME for a particular locale.  However, the same code under Windows 7 fails to enable the IME and set it to the desired locale.  Therefore the correct charcters are not typed.

I am actually building my project with VS 2010, but that was not a choice below.
Sign in to post a comment.
Posted by Rich Chinnici on 2/25/2013 at 5:16 AM

Thank you for your response, but the Korean Keyboard/IME was already activated on our machines.

This problem was resolved with the help of David Wooden - Senior Escalation Engineer from Microsoft Developer Support. I needed to change the value of the Korean locale ID as follows:

public const string localeKorean = "00000412"; //"e0010412";

The higher order bits being set to something other than zero was causing "undefined behavior". When I corrected the value, everything worked properly.
Posted by Microsoft on 2/21/2013 at 1:54 PM
Thank you for your feedback, Rich.
In order for your sample application to work on Windows7, please activate Korean IME keyboard service. Go to "Control panel", type "input method" in the search box on the right, select "Change keyboards or other input methods" option, as a result a "Region and Language" dialog will appear, please click "Change keyboards..." button in this dialog, as a result "Text Services and Input Languages" dialog will open, click "Add" button to select all desired input languages. Save your changes.
If this issue still reproduces at your end, we would like to investigate it again. Please provide the exact steps/actions to reproduce the problem, reactivate this bug and we will re-investigate.
The Windows Forms Product Team
Posted by Microsoft on 12/4/2012 at 10:39 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 12/4/2012 at 8:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(