How can .NET replace COM?

From: Robert Wehofer (thalion77_at_graffiti.net)
Date: 08/31/04


Date: Tue, 31 Aug 2004 16:27:37 GMT

Hello!

I would like to know, how .NET could replace COM? How is it possible?

Imagine an application, which is a COM server, where a client could get
informations or call functions (e.g. I would like to know the name of the
current opened project in the application). The client has to reference the
current running COM server (in VB you use GetObject). Then I get
informations about the current running application.

How can .NET live up to that expectations?
You can reference certain assemblies, but those assemblies are loaded
explicitely to the process of my application. How can I reference to an
already loaded assembly. Do you need .NET remoting for that demand?

Robert



Relevant Pages

  • Re: soapsuds
    ... > the 'server' assembly, then the soapsuds extraction falls over. ... > in .Net that namespaces cannot span assemblies? ... > interface defined in a shared assembly (which can be implemented my other ... dll which sits both on the server and the client allowing objects to talk to ...
    (microsoft.public.dotnet.framework.remoting)
  • A tricky one for a beginner
    ... This is what I want to do: Save an object's data to a SQL Server 2000 ... - Many client machines. ... declarations of the business objects) that is shared by both the client ... and server object libraries - so that both have a reference to the ...
    (microsoft.public.dotnet.distributed_apps)
  • A tricky one...
    ... This is what I want to do: Save an object's data to a SQL Server 2000 ... - Many client machines. ... declarations of the business objects) that is shared by both the client ... and server object libraries - so that both have a reference to the ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: A tricky one...
    ... This is what I want to do: Save an object's data to a SQL Server 2000 ... - Many client machines. ... declarations of the business objects) that is shared by both the client ... and server object libraries - so that both have a reference to the ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: "Insufficient state to deserialize the object" error
    ... The delegate itself is a serializable object, so both client and server need ... > that requires serialization? ... >> If any of the assemblies are being loaded from the mapped drive, ...
    (microsoft.public.dotnet.framework.remoting)