Re: Best IPC mechanism between managed C# and unmanaged C++

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Pavel Minaev wrote:
On Nov 21, 11:40 am, Bob <B...@xxxxxxxxxx> wrote:
The question about IPC between managed vs unmanaged comes up once in a
while, and I generally see "Named Pipes" as the answer. But I was
wondering if there is anything new.

The app in this case will only be sharing short strings for the most
part, and the C++ part will eventually be rewritting in C#. So I'm
looking for anything that's fast and easy, but also not too ugly. Is
it still necessary to use named pipes?

Do you actually need _inter-process_ communication? If so, named pipes
are still the fastest available communication mechanism for that, and
relatively easy to use as well, no matter whether you're using C++ or
C#.

Is named pipes faster than shared memory ?

Arne
.

Relevant Pages

  • Re: Best IPC mechanism between managed C# and unmanaged C++
    ... and I generally see "Named Pipes" as the answer. ... The app in this case will only be sharing short strings for the most ... relatively easy to use as well, no matter whether you're using C++ or ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Best IPC mechanism between managed C# and unmanaged C++
    ... and I generally see "Named Pipes" as the answer. ... The app in this case will only be sharing short strings for the most ... relatively easy to use as well, no matter whether you're using C++ or ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Serial Monitor
    ... Grant Edwards wrote: ... [debug serial traffic w/pipes] ... on named pipes. ... of the app to work with a named pipe. ...
    (comp.os.linux.development.apps)
  • Re: Using Named Pipes ?
    ... Unfortunately I don't have specific links to "named pipes" implementations ... | Im looking for a way use named pipes between a service app and an app run ...
    (microsoft.public.dotnet.languages.vb)
  • RE: can not generate SSPI Context
    ... Try switching the protocol using the Client Network Utility to Named Pipes. ... Instead of using your vb app, you can test with the following command line ...
    (microsoft.public.sqlserver.security)