Hello,
I wasn't sure where to put this topic so please move if you need to.
I've updated to 13.1 (including the latest service release) and I've been seeing this in my application more and more (I'm not able to provide a sample project at the moment due to deadlines).
Can anyone think why this might be? The latest sample is where I'm simply trying to show a form. I also see this sometimes when the application starts up in the splash screen (even if I add exception handling around this it gets thrown as an unhandled exception regardless which makes me think it's an internal issue):
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.NullReferenceException: Object reference not set to an instance of an object. at Infragistics.Win.Misc.UltraButton.OnLostFocus(EventArgs e) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Thanks,Andrew
Hello Andrew,
I have logged a development issue for this.
You can view the status of the development issue connected to this case by selecting the "Development Issues" tab when viewing your active cases on the web site.
Hi Michael,
Apparently my case has been closed however it says the following under development issues "There are no development issues associated with this support request."
Hallo,
PLEASE HELP! Same problem here. Customers getting nervous ;(
Will there be a Service Patch in closer future?
Nico
Hi,
The NullReferenceException in the OnLostFocus of UltraButton will be fixed in the next Service Release.
According to the Infragistics Product Service Releases Schedule, the estimated release date is June 21st.
Thank you so much Mike.
For those of you following this topic, here's an update:
"Thank you for contacting Infragistics Developer Support.
Subject: Development Issue #143528 to be released soon Issue "143528: NullReferenceException encountered in OnLostFocus method" has been fixed and verified by our Engineering Team in the following versions WinForms_2013.2, WinForms_2013.1, WinForms_2012.2.
We are in the final stages of creating the service release and expect to publish it according to following schedule:
http://ko.infragistics.com/help/service-releases/ "
Thanks for getting this sorted Michael.
Regards,
Andrew
Be useful to be able to look bugs up - I don't seem to be able to find a searchable area..
In this instance the bug also seems to exist in v12.1 : 12.1.20121.2135 but it does not exist in 12.1.20121.1001
So how do I find exactly when this bug was introduced if I can't look up details..?