I am trying to troubleshoot an error that I cannot reproduce, but I'm hoping that I can get some clarification on part of the stack trace. Unfortunately, all I have is the screenshot because the user closed out of the dialog without copying the stack trace.
It throws an object ref error when it tries to access the RemoveAllColumnReferences property of the UltraWinCalcManager. Problem is, this object got disposed in the line previous. Any ideas why Infragistics seems to try to access the property of a disposed object?
Hello.
This issue has been fixed in the latest service release. You can download and install it at http://www.Infragistics.com by looking in the My Keys and Downloads section. Have you had a chance to download and install the service release to test it?
Hi,
I have logged this behaviour with our developers in our tracking system, with an issue ID of 32389. This development issue will be assigned to a developer to research for a fix, workaround, or other resolution. If some other resolution is reached, I will contact you with this information.
You can view the status of all development issues connected to this case from the "Development Issues" tab, when viewing this case on the "My Support Requests" page of our website. I hope this helps. Please let me know if you need further assistance on this issue.
We are still using v8.3, but will be upgrading as soon as we have the time to go back through our app and test the new version.
The RemoveAllColumnReferences call is inside the Dispose Method. So this is not being called After the object has been disposed, it's being called as part of the process of disposing it.
I took a look at the code and there is a potential null reference there. I can't see any way that the particular object in question could ever be null, but clearly it's happening in your case and needs to be accounted for.
I'm going to forward this thread over to Infragistics Developer Support so they can write it up for developer review.
But you should be aware that the oldest version still be updated is v9.2. So if you are using an older version than that, you will need to upgrade in order to get the fix.