Actually, it could be the LocalizationDesigner problem that we just recently uncovered.  All of the people that created custom controls that inherited our controls would crash VS when they dropped a control on the form.  Turned out that it was a problem within the LocalizationDesigner throwing an OutOfMemoryException when it got into an infinite loop of recursive calls.

There's a good chance that it might be the same problem. 

Here is the link to the newest Extensibility DLL that might resolve the problem.  No promises, but, it might work

http://forum.strataframe.net/FindPost9739.aspx

Thanks for the info.

Well, the reason the message is ambiguous is because the problem is coming from something in your environment.  Yes, I have seen the message before and it generally because of a custom control or designer setting that is causing the problem....and something I have done.  You are going to have to work backwards pulling things out until you find your problem.

Most times I am trying to do something in design-time which should only be executed at run-time within a custom control and need to test on the DEsignMode property of the control.

Has anyone else ran into this problem?







I have NO idea how to go about trouble shooting this. Of course I've started with Google. ;-)



Any and all suggestions would be appreciated.