VS2010 IDE Freezing on Edit Items
-
I have two VS2010 WinForms applications that are very similar to each other. Both have a MenuStrip and a StatusStrip. Whenever I attempt to edit the items on either control in either application VS freezes, and as far as I know, never returns. I've waited up to 10 minutes with nothing happening. I've had one other developer test one of the solutions on his PC and they didn't have this problem. As a test I opened a different WinForms app that also contained a MenuStrip and StatusStrip in VS2010 and I have no problems editing the items for that application. It doesn't seem to matter how I try to edit the items, clicking the Edit Items link in the popup, or the Collection button in the properties window, or the Edit Items link at the bottom of the properties window, they all cause the IDE to freeze. In an attempt to resolve this I've deleted both the MenuStrip and StatusStrip and replaced them one at a time, no change. I've copied all of the controls from one application to a brand new application, including any custom control code, I can edit the items in the new application with no problems. Creating a new application adding new controls also allows me to edit the control items. I've compared the designer code between a non-working and working app for the StatusStrip and nothing seems odd to me. We're all running Windows 7 Professional 64-bit, there's really no reason this should be freezing the IDE the way it is, and doing it just for me. I've spent some time on the Internet looking for anyone else reporting similar problems and didn't really find anythihng. Has anybody seen this before and do you have a good solution? I'd really prefer not to copy/paste the code into a brand new application. Although, that may be my only choice. [Edit] I found out what the issue was and in case anyone else runs into this here's the explanation. This is caused by a circular reference. Why this causes controls to hang when attempting to edit their items, I have no clue. To put it simply, we have two applications compiled as dlls (A.dll, B.dll), both are launched by the same menu application. Both of the applications reference each other, e.g. A.dll references B.dll and B.dll references A.dll. This is done so each application can load the other and pass certain data to the other application to perform an auto-lookup. I discovered this by creating a completely new solution for A.dll and copying all the code files from the original solution into the new solution. Once I got the solution to compile I