Now I know what you're talking about. No, there is nothing you can do about it. This is something that happens in Windows Forms. I haven't been able to find anything documenting what's causing it. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

I mean exactly what BadKarma says. Have you ever done a large project without command line compiling/linking? Is it worth planning in advance that the project be compiled in command line, possibly later in the development cycle?

The .NET Framework can handle this number of controls easily. The question becomes is the layout being setup correctly in your code? What the designer lays out when you drop the controls in place, visually might look OK, but in fact, your control is actually not in the container that you dropped it on. You might want to go through your designer generated code and follow it step-by-step to see which containers your controls are actually ending up in. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Hi Steve, In Visual Studio 2005 it is a bit different, but close enough to your description so I have found it. Definitely, struggling with VC++ at 5:00am was not very productive work. :) Thanks much, man! Nick

My response for Question 1 The Mediator design pattern gets used to coordinate communication between many colleagues. This would apply to your situation if that communication needed to exist. The Publisher-Subscriber pattern exists for one-way communication, from the Publisher to the Subscriber. From your description of the application, I agree that you have used the correct design pattern for the situation. However, you may need to reconsider your implementation since so much depends on your Publisher interface. My response for Question 2 Your Publisher-Subscriber framework should handle this. Instead of publishing to a local object (in the same process), it uses some sort of IPC. How this gets done depends on your implementation. However, if you've defined your Publisher-Subscriber interfaces correctly, you should have the ability to replace the classes that implement intraprocess communication with interprocess communication. Many RPC frameworks exist; for a starting point, check out Wikipedia[^]. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty

Thank you, Joaquín. It is pretty unfortunate that an ISO standard is not supported but I am going to follow your suggestion and avoid exception specifications. Thanks again!