Why not embed the resources in the plug-in assemblies, and use the same
mechanism you use to load the plugins to load their resources?
M
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED]] On Behalf Of Peter Zaborski
Sent: 31 May 2002 16:41
T
ngs as you found them wrt to the pool's thread context. I think
that's faintly rude!
Matthew Adams
-Original Message-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Chris Sells
Sent: 29 May 2002 16:10
To: [EMAIL PROTECTED]
Subject: [DOTNET] Putting bits of UI o
Thinking about it, I guess one possible application would be a
multiple-window SDI type application where you wanted several,
independent top-level peers, but didn't want to start multiple
processes?
Matthew
-Original Message-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf
use Control.Invoke to get the
real work done on the right thread.)
--
Ian Griffiths
DevelopMentor
- Original Message -
From: "Matthew Adams" <[EMAIL PROTECTED]>
> How would the Form know that it needed to throw an exception? As I
said,
> there is nothing intrins
How would the Form know that it needed to throw an exception? As I said,
there is nothing intrinsically wrong with creating the Form and calling
Show() from the Timer thread. The 'no-return' behaviour you get is, I
guess, because a message pump is started when you create the first
window on a thre
Not in this case. You can quite happily create a window on another
thread. You just musn't call any of its methods from any other thread;
multiple GUI threads are fine.
The problem with this particular case is that you are doing it on a
thread pool thread, and it is considered bad manners to do t
