I am now getting an 'InvalidOperationException' error when I exit my applicaiton. The error message is 'DragDrop registration did not succeed'. When I copy the whole error to the clipboard, this is what I get:
System.InvalidOperationException was unhandled Message="DragDrop registration did not succeed." Source="SharpUI.Toolbars" StackTrace: at DataDynamics.SharpUI.Toolbars.BandCollection.Clear() at DataDynamics.SharpUI.Toolbars.UiToolbarManager.Dispose(Boolean disposing) at System.ComponentModel.Component.Finalize()
I am due to release my app very soon and this sort of thing is making that impossible. Please help me resolve this issue and the issue I posted yesterday.
No I can't. First of all, my app is in VB.NET, second the fault is intermittent and third, I have no idea of the cause so how exactly do you suggest I modify the sample so that you can see the exception being thrown.
Instead of trying to get me to do all the work, why don't you look at the code in the 'BandCollection.Clear' routine and attempt to determine where an 'InvalidOperationException' error could occurr and once you figure that out, try fixing it. I can't imagine there are that many places where the message 'DragDrop registration did not succeed' would be generated.
As a programmer of 15 years myself, I appreciate the difficulty of fixing an issue that you can't replicate but you simply can't put the onus back on the customer. I have purchased your product in good faith expecting it to be reliable and generally bug free (not totally bug free of course). I personally come across these situation regularly but I make absolutely every effort to figure out the problem myself before I go back to the customer and even then, I certainly don't presume that if they provide me with an example that doesn't work on their system that it won't work on my system also. Chances are, it will work fine on my system but that does not mean that the problem is theirs. It would still be my program that was erroring and therefor my problem to solve.
Please either provide me with a code based work around that I can use to prevent the problem occurring or a service pack that fixes the problem. That goes for my previous issue also.