Also that article is using the system32 dlls to get the job done. tons of
I did, but now that I remember a little more, I couldn't use that because
the other app was native, and was sending the WM_COPYDATA message. I guess
that problem wasn't entirely .Net's fault.
AliR.
"Ajay" <ajaykalra@yahoo.com> wrote in message
news:e4f12315-e6ec-4eaf-966e-bb8d4ee40bd4@e38g2000vbe.googlegroups.com...
On Apr 9, 12:17 pm, "AliR \(VC++ MVP\)" <A...@online.nospam> wrote:
Another example of having to go down to win32 dlls was for inter-process
communication. I don't know why .Net does not have this built-in. I had
to
revert back to native SendMessage and WM_COPYDATA to get that
functionality.
I havent done this in .Net but I would be surprised if it was missing.
Did you look here:
http://www.codeproject.com/KB/threads/dotnetnamedpipespart1.aspx
--
Ajay