We encounter a bug in winform application in .net 2.0 that
often when we press continually on a NumericUpDown control the
application crash with the following exception :
System.NullReferenceException occurred
Message="Object reference not set to an instance of an object."
Source="System.Windows.Forms"
StackTrace:
at
System.Windows.Forms.UpDownBase.UpDownButtons.TimerHandler(Object
source, EventArgs args)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message&
m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr
hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at
System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32
dwComponentID, Int32 reason, Int32 pvLoopData)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
Stoitcho Goutsev (100) - 10 Jan 2007 15:18 GMT
Pavel,
Can you post compilable sample that demonstrates the problem?

Signature
Stoitcho Goutsev (100)
> We encounter a bug in winform application in .net 2.0 that
> often when we press continually on a NumericUpDown control the
[quoted text clipped - 24 lines]
> reason, ApplicationContext context)
> at System.Windows.Forms.Application.Run(Form mainForm)