Hi,
I have attached a simple project that (I believe) shows a breaking change from 8.2 to 9.1. I have added a grid with a couple of bound columns and one unbound column, a checkbox (Boolean). If you build in using the 8.2 infragistics references, turn on exception handling (break at exceptions), and run, you will see..... NO PROBLEM! You can go from one checkbox to the other to your heart's content.
However, if you build with 9.1 you will get the first chance exception "Invalid cast from system.boolean to system.windows.forms.checkstate", when you start checking the checkboxes. I believe it occurs as soon as you leave the first checkbox.
What happened?
My concern is twofold...
1) I'm wondering if I coded things up in the best way possible. Perhaps the change to 9.1 is exposing something I did wrong (sloppy code) and got away with in 8.2?
2) Even though it's a first chance exception and you don't see it unless you have exception handling turned on, it's annoying in our large project (which is not included). When one is trying to find an actual problem, one often turns on "break at exceptions". It's a pain to see "false alarms". Our main project has few if any first chance exceptions occurring. I hate to be the one to introduce one.
Can you let me know what's going on?
And of course, tell me when I can expect an offer to join your QA department, or failing that, get a personal copy of the Infragistics suite so I can provide you with more valuable feedback :)
Thanks, and keep up the good work. In general, I find you controls easy to work with and much better than some other third party gui controls I could mention!
-Andrew
I took a look at your sample, and I am able to reproduce the same issue using v8.2 - but I am, of course, using the latest service release. So it appears that this problem was introduced by a recent bug fix and not neccessarily just in v9.1.
This may be a necessary change in order to fix another issue, but I can understand how it might be annoying. It's also not very efficient, since exceptions tend to slow things down.
I'm going to forward this thread over to Infragistics Developer Support so they can check it out and see if we can find a way to do what we need without raising an exception.
Thanks Mike.
Let us know if it's fixed in 9.2 (or whatever). It might affect our decision on when to upgrade.