> I believe it gets down to one message pump handling
> UI messages--since each message pump needs to be on
> it's on thread there can be only one UI thread.
Win32, and WinForms, both *definitely* support having more than 1 UI thread
per process. You need to "do the right thing" in WinForms, whic
The main reason that methods are not virtual by default in C# is because
virtual methods allow derived classes to alter the contract between a base
class and the user of a class, without the base class having any control
over how this is done, or even knowledge that this is being done. In other
wo
The WCF on A does not necessarily know that the connection has failed until
you try to make use of that connection. This is a fundamental property of
packet-switched networks. Unless you are using a keep-alive to detect the
loss of the peer, there is no way to detect that the peer is
gone/dead/un
My old problem is easily re-creatable.
1) create a new winforms project.
2) add a menu on the form with an iteam
3) build
4) add another form that inherits the first form
5) add code to handle the click event of the menu item in the other form.
When you say "other form", you mean the first form
> If we modify the base form in any significant way, the
> generated code in inherited forms or their resource files
> will often become corrupted and we have to correct the
> situation by hand. This can be a very time consuming and
> frustrating process. If the base form is left alone, then it
