I had a problem in a version of VWG nearly a year ago where, after getting to a certain point of complexity with the application, I would consistently get a Visual Studio error dialog indicating "Cannot access disposed object" of type "DesignerFrame." I had discussed it on the forums here and in the customer forums, but it couldn't be reproduced.
I just had the same problem with VS2010 and VWG 6.4 (note, this only happens when designing VWG applications). Googling around, I find that the issue had been reported to Microsoft and they had finally tracked it down to DevExpress controls, so closed the problem as external to Visual Studio.
Unfortunately, I don't have DevExpress controls installed, but I believe the same issue that rose up with those controls is also present in the VWG design package. It seems that the DevExpress problem is fixed in their tools, which is excellent news since it indicates that the problem is traceable and solvable. More details can be found here.
I don't know if anyone has run into this besides me, but I can't believe that I create the nastiest UIs in the customer base. Maybe it's just the combination of controls I favor that cause the issue? But I would love someone at Gizmox to read through what's been documented on connect.microsoft and possibly even contact the DevExpress folks if it would help track it down. I'm absolutely convinced the problem is in the VWG designer code, as I've never seen this behavior when not working VWG interfaces.
Any help you can provide would be most welcome.