So I go to uninstall SF and start over (again) and I get this...see attachment.

When you installed SF 1.7.0, it did not clear out all of the 1.6.0 assemblies (which can be caused by several things). Before you get much deeper, manually remove any 1.6.0 references then reload the 1.7.0 build. Make sure that all of your files get updated to the 1.7.0 version otherwise you will have other weirdness.



Second, download the SF source code, build it in debug mode, which should also update your GAC references. THEN, get out of VS. Open VS back up and you should have SF DLLs in debug mode which will allow you to debug and break on any exception allowing you to trace and see where the point of failure is, look at a stack trace, etc.



I really think that you are dealing with an issue within your code. For example, something is causing the grid to re-evaluate the bound data source which is causing the error.



First, before you go crazy, just override the OnFormClosing method of the form, and manually remove the data source form the grid:







If you are using VB.NET then replace the null with Nothing. That should prevent anything from trying to evaluate the BBS on the form close.

Attached are two assemblies and their version tabs. Is the business.dll supposed to have an assembly version of 1.6?

References...how do I cleanup the references? I attached a window shot of the Add References for a project. Two of the references I need in the project are version 1.7.0 but the other two are 1.6.0. Ugh! I assume that is not correct.



I have uninstalled and reinstalled so many times. What is my best path for fixing this issue?

The C# app sample is complete. There are no errors in that sample app....so, I am totally vexed and befuddled. What do I do, now?

I attempted to recreate the error for you in a sample application. The app that I created was a VB app. I am not getting the same error (although, I forgot to fill the BO). Of course, we are not dealing with apples and apples, so I am going to create a C# app, instead. Stand by.

I dropped a DataGridView onto the form and disconnected the DevEx grid from the main BBS (I left the two repository BBSs connected). I connected the main BBS to the DataGridView. When closing the form, I got the same error. So, I deleted all of the BBSs. Ran the form, closed it and received no error. Then, I added a new BBS to the form and wired it to the DataGridView. I ran the app, opened the form, saw the data in the grid, then closed the form. No error! I then wired only the main BBS to the DevEx Grid. When closing the window, it generated the same error. So, the combination of the DevEx grid (9.1.5) and the BBS (versions 1.6.6, 1.6.7 and 1.7.0) makes the window fail on closing. The dispose method...inserting my guesswork here...seems to be trying to get rid of objects that may have already been dumped via the DevEx grid disposal process.



Thoughts?

Before you spend too much more time, just drag a DataGridView onto your dialog and see if you experience the same problems. Grids are always a pain and since they are so "fat" they can introduce tings at times do to forces outside of SF. As such, I always get back to basics when I see strangeness like this.



Let me know...and again, I really am sorry for the long delay...I just lost this thread to the abyss....but now it is found

Hi Trent,



I figured you were busy wrapping up the release. A LOT of nice stuff in there. Thanks a bunch for the new features and functionality!!



As far as a sample...I will try. I experience the error only when a BBS is employed to fill a DevEx XtraGrid object. I do not get the error in any other way. I have not tried a standard grid. If I get the opportunity to produce a sample, I'll include both. I am just now setting up the Inventory Adjustments window to issue a breakpoint during the close event. Hopefully, I can see something going on there. Fortunately, I was able to get the designer working again on that window.



I'll keep working on it and updating you on the steps I am taking.



Thanks for checking in!

Bill

Bill,



Sorry for the delay here, we have been fighting some internal ISP issues and trying to get the 1.7 build out the door, so a few things fell between the cracks...so BIG apology on this!



OK, is it possible to create a small sample that you can send me so I can see what you are fighting here? It is possible that the DevEx grid is doing something odd (would not be the first time) but I would like to see if it can be reproduced using a standard DataGridView as I would imagine that the issue you are fighting is not related to the DevEx grid but rather instantiation or something along those lines.



A sample, if possible, would drastically move time to the left on this. Thanks!