Thanks for the response - sounds like a good idea. But I am not familiar
with the Reflector you mention. Could you provide a link? (Are you thinking
of Rotor?)

"Cool Guy" <(E-Mail Removed)> wrote in message
news:1gakpgp121338$.(E-Mail Removed)...
> Craig Bryant <(E-Mail Removed)> wrote:
>
>> Does anyone have any idea what I can do, in the SendMessage case, to get
>> the behaviour I am seeing using Control.Invoke()? I would rather not use
>> Control.Invoke() because it has a couple limitations relative to using
>> SendMessage() (but I may have to...)
>
> It might be rewarding to look at the code for Control.Invoke in Reflector.

Craig Bryant <(E-Mail Removed)> wrote:

> Thanks for the response - sounds like a good idea. But I am not familiar
> with the Reflector you mention. Could you provide a link? (Are you thinking
> of Rotor?)

No, this: <http://www.aisto.com/roeder/dotnet/>.

With it you can view C# code, for example, representing compiled MSIL. So
you could use it to view the innards of Control.Invoke.

Contorl.Invoke does a PostMessage then waits on a kernel event object which the UI thread signals when it has invoked the method

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

Thanks for the response - sounds like a good idea. But I am not familiar
with the Reflector you mention. Could you provide a link? (Are you thinking
of Rotor?)

"Cool Guy" <(E-Mail Removed)> wrote in message
news:1gakpgp121338$.(E-Mail Removed)...
> Craig Bryant <(E-Mail Removed)> wrote:
>
>> Does anyone have any idea what I can do, in the SendMessage case, to get
>> the behaviour I am seeing using Control.Invoke()? I would rather not use
>> Control.Invoke() because it has a couple limitations relative to using
>> SendMessage() (but I may have to...)
>
> It might be rewarding to look at the code for Control.Invoke in Reflector.



[microsoft.public.dotnet.framework]

Thanks a lot, Richard.

"Richard Blewett [DevelopMentor]" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> Contorl.Invoke does a PostMessage then waits on a kernel event object
> which the UI thread signals when it has invoked the method
>
> Regards
>
> Richard Blewett - DevelopMentor
> http://www.dotnetconsult.co.uk/weblog
> http://www.dotnetconsult.co.uk
>
> Thanks for the response - sounds like a good idea. But I am not familiar
> with the Reflector you mention. Could you provide a link? (Are you
> thinking
> of Rotor?)
>
> "Cool Guy" <(E-Mail Removed)> wrote in message
> news:1gakpgp121338$.(E-Mail Removed)...
> > Craig Bryant <(E-Mail Removed)> wrote:
> >
> >> Does anyone have any idea what I can do, in the SendMessage case, to
> >> get
> >> the behaviour I am seeing using Control.Invoke()? I would rather not
> >> use
> >> Control.Invoke() because it has a couple limitations relative to using
> >> SendMessage() (but I may have to...)
> >
> > It might be rewarding to look at the code for Control.Invoke in
> > Reflector.
>
>
>
> [microsoft.public.dotnet.framework]

Thanks for the info.

"Cool Guy" <(E-Mail Removed)> wrote in message
news:2ozacz49te5g$.(E-Mail Removed)...
> Craig Bryant <(E-Mail Removed)> wrote:
>
>> Thanks for the response - sounds like a good idea. But I am not familiar
>> with the Reflector you mention. Could you provide a link? (Are you
>> thinking
>> of Rotor?)
>
> No, this: <http://www.aisto.com/roeder/dotnet/>.
>
> With it you can view C# code, for example, representing compiled MSIL. So
> you could use it to view the innards of Control.Invoke.