Hello,
By analyzing these logs this morning, we have discovered a new type of error that causes our application to fail many times by a day at one of our clients, the error shows that the interop class Windows was called by the graphics library Telerik.
2016-11-08
09:55:02,344 [1] ERROR Logger -
System.TypeInitializationException:
Une exception a été levée par l'initialiseur de type pour 'Telerik.Windows.Controls.InternalWindow.Standard.DpiHelper'. ---> System.ComponentModel.Win32Exception: L’opération a réussi
à
Telerik.Windows.Controls.InternalWindow.Standard.NativeMethods.GetDC(IntPtr
hwnd)
à
Telerik.Windows.Controls.InternalWindow.Standard.DpiHelper..cctor()
--- Fin de la trace de la pile d'exception interne ---
à
Telerik.Windows.Controls.InternalWindow.Standard.DpiHelper.DevicePixelsToLogical(Point
devicePoint)
à
Telerik.Windows.DragDrop.DragDropManager.UpdateWindowLocation()
à
Telerik.Windows.DragDrop.DragDropManager.CreateDragDropWindow(Object content)
à Telerik.Windows.DragDrop.DragDropManager.DoDragDrop(DependencyObject
dragSource, Object data, DragDropEffects allowedEffects, DragDropKeyStates
initialKeyState, Object dragVisual, Point relativeStartPoint, Point
dragVisualOffset)
à
Telerik.Windows.DragDrop.DragInitializer.StartDrag()
à
Telerik.Windows.DragDrop.DragInitializer.StartDragPrivate(UIElement sender)
à
Telerik.Windows.DragDrop.DragInitializer.DragSourceOnMouseMove(Object sender,
MouseEventArgs e)
à
System.Windows.Input.MouseEventArgs.InvokeEventHandler(Delegate genericHandler,
Object genericTarget)
à
System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
à
System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target,
RoutedEventArgs routedEventArgs)
à
System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs
args, Boolean reRaised)
à
System.Windows.UIElement.RaiseEventImpl(DependencyObject sender,
RoutedEventArgs args)
à System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs
args)
à
System.Windows.Input.InputManager.ProcessStagingArea()
à
System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
à
System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
à
System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd,
InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y,
Int32 wheel)
à
System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd,
WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
à
System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg,
IntPtr wParam, IntPtr lParam, Boolean& handled)
à MS.Win32.HwndWrapper.WndProc(IntPtr
hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
à
MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
à
System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback,
Object args, Int32 numArgs)
à
System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate
callback, Object args, Int32 numArgs, Delegate catchHandler)
Did you ever experience this problem?
1 Answer, 1 is accepted
We are not aware of such an issue with the current version of UI for WPF. Can you please share some more details regarding the exact scenario? If you can provide a sample project that would be really helpful. Also can you confirm which version of the controls are you using? Can you try upgrading to the latest release if you are using older one and see whether the issue is still present?
I'm looking forward to hearing from you.
Regards,
Kalin
Telerik by Progress