dotnet interop: IPC is very bad in framework -- dotnet interop

Re: IPC is very bad in framework

Dino Chiesa [MSFT]
7/31/2003 9:32:22 AM

dotnet interop: I am not sure what you mean. There are a number of ways to do inter-process
communication in .NET.
Among them:

1. Web Services - this is probably the most general

2. .NET Remoting

3. Memory mapped files.
see, for example, http://www.mvps.org/windev/dotnet/ and look at FileMap

4. use SendMessage (dllimport:user32.dll) to send Windows Messages to other
local Windows applications (not necessarily built with .NET).

Also see
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconchoosingcommunicationoptionsinnet.asp
[quoted text, click to view]

IPC is very bad in framework

Ville Pirhonen
7/31/2003 3:02:48 PM

I have been reading this newsgroup quite often, and quite many are stuck
with
problem of proper IPC in Framework.

This is my humble opinion:

It is very very bad that there is no proper IPC tools in .NET environment.
If I have got things right, the CLR is in the way of IPC. There is no
implementation for low level IPC between binaries, in example your .NET
service and .NET frontend that will manage service, the communication is
very difficult. That's very stupid.

I have used MMF, to do IPC, but it's old technology. It's very very sad that
there is not good IPC in .NET or should I say CLR.

Ville Pirhonen