Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
1415
Exception Thrown since upgrading to 2013.2 - UltraToolbarsManager
posted

I upgraded to Winform 2013.2 and changed my ribbon style to 2013 .. now I am seeing a new exception.

We have also moved to running our app on 2012R2 from 2008 not sure if that is related.

2013-12-11 12:37:16 PM : V1.0.0.617: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> 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.Form.CreateHandle()
   at System.Windows.Forms.Control.RecreateHandleCore()
   at System.Windows.Forms.Form.RecreateHandleCore()
   at System.Windows.Forms.Control.RecreateHandle()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.ForceRecreateHandle(Form control)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnThemeChanged(Object sender, EventArgs e)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Infragistics.Win.WeakReferenceMulticastDelegate`1.WeakReferenceProxyEventHandler.OnEventFired(Object sender, EventArgsType e, Type delegateType)
   at Infragistics.Win.WeakReferenceMulticastDelegate`1.Invoke(Object sender, EventArgsType e)
   at Infragistics.Win.XPThemes.OnThemeChangeMessage(Object sender, EventArgs e)
   at Infragistics.Win.XPThemes.ThemeManagerWindow.OnThemeChanged(EventArgs e)
   at Infragistics.Win.XPThemes.ThemeManagerWindow.ThemeManagerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

  • 29105
    Offline posted

    Hello Greg,

    I am going to require more information regarding your application.

    1. What seems to trigger this issue?
    2. Can this issue be reproduced? How? Please provide steps.
    3. Is this a runtime or design time issue?
    4. What does your application consist of? Please provide screenshots.

    In order to properly assist you I require an isolated sample that demonstrates the issue.