Problems on .NET Framework v1.1???

[Bill Triantafyllos]

Hi,



About 2 months ago we have switched to .Net Framework v1.1 and lately we
have seen exceptions generated on some of our applications, which have been
developed more than a year and a half ago.



The exceptions seem to be generated in some random fashion, that is, it is
hard to reproduce in a consistent manner. Moreover, the exceptions are
generated while navigating the UI, which consists of WinForm controls and
third party (DevExpress) controls.

Once the exception is initially generated it keeps been re-generated for as
long as you keep navigating the UI. Most of the time, exiting the
application and then restarting it, is sufficient to get rid of the
exception. In other cases rebooting does the trick.



More specifically, the following exception has been noticed while navigating
a DevExpress grid control (tabbing through the grid's columns, or
collapsing/expanding a master-detail view). Also, the exception has been
noticed while clicking on a System.Windows.Forms.LinkLabel control:



Exception # 1:

System.Windows.Forms:

Object reference not set to an instance of an object.

at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd,
Int32 msg, IntPtr wParam, IntPtr lParam)

at System.Windows.Forms.Control.ProcessUICues(Message& msg)

at System.Windows.Forms.Control.PreProcessMessage(Message& msg)

at
System.Windows.Forms.ThreadContext.System.Windows.Forms.UnsafeNativeMethods+
IMsoComponent.FPreTranslateMessage(MSG& msg)







In addition the following exceptions have been noticed during UI navigation
but more rarely than the one above:



Exception # 2:

External component has thrown an exception.

at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr
wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)

at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)

at System.Windows.Forms.Control.DefWndProc(Message& m)

at System.Windows.Forms.Control.WmUpdateUIState(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam).





Exception # 3:

System.Drawing:

A generic error occurred in GDI+.

at System.Drawing.Graphics.CheckErrorStatus(Int32 status)

at System.Drawing.Graphics.DrawString(String s, Font font, Brush brush,
RectangleF layoutRectangle, StringFormat format)

at System.Windows.Forms.Label.OnPaint(PaintEventArgs e)

at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e,
Int16 layer, Boolean disposeEventArgs)

at System.Windows.Forms.Control.WmPaint(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Label.WndProc(Message& m)

at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)





As I mentioned the exceptions are not reproduced in a consistent manner. At
this point I do not know if the exceptions are a result of our apps, the
third party controls or the .Net Framework. Does anyone have experienced
any similar issues when upgraded to .Net v1.1??

I will appreciate any input.





Thanks,



Bill.

 

[Guest]

We are receiving the same error while using a 3rd party control when pressing a hotkey to close the window and open another window inside an MDI application. We are using version 1.1.4322 of the .Net framework. This error is quite transitive. We have not found a pattern as to when it occurs. Were you able to find any additional information or a fix for this error?

Thanks,

Joanna