Member Avatar for jineesh

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception: Error creating window handle.
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.TextBoxBase.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at Elegant.Ui.TextBoxBasedControl.TextEditorContainerWndProc(Message& m)
at Elegant.Ui.TextBoxBasedControl.TextBoxContainer.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I have attached a screen shot of the message i have got. please have a look on it.
why i am getting this error?
any one please help. thanks in advance

error.png 19.77 KB
  • 2 Contributors
  • 4 Replies
  • 543 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by jineesh
Member Avatar for nick.crane

Have you seen this. Are you using the latest version of Elegant.UI?
Is it fully licensed?
Maybe better to go to the tool providers support forum.

Edited by nick.crane because: Added link to support forum
Member Avatar for nick.crane

If you are still having trouble with this then you need to find out where the error is coming from.

If the debugger is not breaking in your code then you might benefit from trapping the first time exceptions. To do this use menu Debug/Exceptions... then check Common Language Runtime Exception to break when first thrown. Now when you debug your program it should break immediately the error occurs at the point in your code where it happens.

You should now try to fix the problem by understanding what causes it, then prevent it from happening.

For those occations when it is not possible to fix the problem then it is possible to trap the error using the try {} catch {} statement.

Note that the first time exception trapping will still break even if you use try-catch. To test your own exception handling code you need to turn this off again.

Member Avatar for jineesh

thank you nick. now the problem is solved.

Member Avatar for jineesh

If you are still having trouble with this then you need to find out where the error is coming from.

If the debugger is not breaking in your code then you might benefit from trapping the first time exceptions. To do this use menu Debug/Exceptions... then check Common Language Runtime Exception to break when first thrown. Now when you debug your program it should break immediately the error occurs at the point in your code where it happens.

You should now try to fix the problem by understanding what causes it, then prevent it from happening.

For those occations when it is not possible to fix the problem then it is possible to trap the error using the try {} catch {} statement.

Note that the first time exception trapping will still break even if you use try-catch. To test your own exception handling code you need to turn this off again.

Thank you nick. you have solved my problem

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.