This posting is provided "AS IS" with no warranties, and
confers no rights.
Quote:> I'm debugging a managed app and want to look at some native data e.g. a
> pointer value. It seems that the de* uses the managed expression
> evaluator even if I'm looking at a native C++ object. Rather than
> to writing to the debug output stream, is there any way to use the native
> expression evaluator in a managed program (that contains unmanaged code)?
As a beginner in using .NET and enterprise services I am faced with a basic
What is the best way for a legacy unmanaged C++ application to acces remote
managed .NET COM+ components: is it DCOM or the new .NET remoting? To me it
seems that DCOM would be more appropriate for the following reasons:
1. It's the natural way for unmanaged code to access remote COM+
components - managed or unmanaged.
2. It doesn't require extra-programming effort on the client side: to supply
.NET remoting to the unmanaged client you have to provide a managed in-proc
COM component acting as a high-level "proxy" that the client would call
3. It most likely introduces some extra-marshaling. Although I lack the
details my feeling is that a direct DCOM call into the remote component
would handle marshaling of arguments+return values more efficiently than a
call into a managed in-proc COM component followed by a .NET remoting call.
Can anybody contradict either of 1., 2., 3. or bring an argument for one way
or the other. What is the best way indeed?
Thanks a lot,
McKesson Information Solutions