We recently had an exception with a strange call stack that just showed some method in the XamRibbonWindow.
Maybe someone else also had this issue and can give any advise as to what may be causing the exception.
The scenario was the following: The user was working in Outlook or Excel and was then moving the mouse over our application window (which was open in the background). While doing that the exception occurred. The user was also working with our application under Citrix.
(Windows 10, .NET 4.7.2 (4.7.3429.0), Citrix: 126.96.36.19910, Infragistics: 16.1)
Thanks for any advise or suggestions.
The complete call stack is:
System.ArgumentException: The root Visual of a VisualTarget cannot have a parent. at System.Windows.Media.CompositionTarget.SetRootVisual(Visual visual) at System.Windows.Media.CompositionTarget.set_RootVisual(Visual value) at System.Windows.Interop.HwndTarget.set_RootVisual(Visual value) at System.Windows.Interop.HwndSource.set_RootVisualInternal(Visual value) at System.Windows.Window.SetRootVisual() at System.Windows.Window.SetRootVisualAndUpdateSTC() at System.Windows.Window.SetupInitialState(Double requestedTop, Double requestedLeft, Double requestedWidth, Double requestedHeight) at System.Windows.Window.CreateSourceWindow(Boolean duringShow) at System.Windows.Window.ShowHelper(Object booleanBox) at Infragistics.Windows.Ribbon.XamRibbonWindow.VerifyExternalResizeWindows() at Infragistics.Windows.Ribbon.XamRibbonWindow.HookProc(IntPtr hwnd, Int32 message, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Using the supported versions of our controls, which at this point are versions 17.1 and later, I have been unable to reproduce the described behavior. Would it be possible for you to send us an isolated sample where the issue can be observed, so I can investigate the matter further?
Looking forward to your reply.
Sincerely,Tihomir TonevAssociate Software DeveloperInfragistics
Thanks for your reply.
We are also not able to reproduce the issue. I just wanted to check if maybe anyone else also had this exception.
I also don't think it's an issue with the XamRibbonWindow, as all the code does is call Window.Show(), so it's more likely that it's an issue with WPF (or Windows).
Thank you for getting back to me. Should you need any help, please let me know.