Cristian Diaconu wrote:
> Well, yes, but I would also argue that, in this particular
> case it's not only performance that is a concern but also
> complexity.
Clearly (to me), the complexity of the CLI (I assume that is what you
mean) was not a big issue for Microsoft. What they tried to do (and
> I would like to know if it is possible to explicitly force a
> thread to run in a particular AppDomain.
Well, the way it works under Windows is that OS threads can cross from
one AppDomain to another freely. But as a CLR programmer, you don't care
about OS threads. They're a platform detail. Y
Jon Flanders showed me this:
stdole.IPicture p = YourFunctionToGetAnIPicture();
Bitmap bmp = Bitmap.FromHbitmap(new IntPtr(p.Handle));
Chris Sells
http://www.sellsbrothers.com/
> -Original Message-
> From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED-
>
Nick,
You have to explicitly load the CLR runtime version "svr vs wks" in an hosting
process, by calling CorBindToRuntimeEx,
just like the asp.net worker process does, Winforms and console type applications
always load the Wks version.
Note when calling CorBindToRuntimeEx to load the server ver
> However, as systems get more and more complex, this is not
> always possible, and a 'business tier' component may have to
> call several other 'business components' (each of which call
> several 'data tier' components) as well as several 'data
> tier' components to complete its task.
Hmm. If I
Hi All,
Does anybody know on how I can convert the IPicture that I get through COM
Interop to a .NET Bitmap object? I've tried Image.FromHbitmap by passing a
IPicture.Handle but was getting an exception.
Thanks... Alex
You can read messages from the Advanced DOTNET archive, unsubscribe from Adv
>First of all, have you read Tim Ewald's book, "Transactional COM+"?
>If not, stop, do not go further until you have. It will change the
>way you do things. For one thing, Tim explains why having two
>objects participate on the same transaction is inherently
>antithetical to scalability. :)
I hav
Hi all,
I am interested in understanding the mechanism of how serviced component is
invoked from a .NET client. I understand that it actually goes through
remoting to get to the service component (I can see the remoting message
sinks all the way to stackbuilder in the stack trace) and uses COM in
