Re: Named pipes class for .NET - 09-28-2009 , 01:12 PM
* David Thielen wrote, On 28-9-2009 19:01:
connection based on a great number of protocols, including Named Pipes
based on code or configuration. It would be reasonably easy and allows
for other ways of communicating if needed.
jesse.houwing at sogeti.nl
Re: Named pipes class for .NET - 09-28-2009 , 01:34 PM
There's nothing wrong with named pipes, and if anything, the security is a
good thing. NamedPipeClientStream (and server) seem pretty straightforward.
There's also .NET remoting (or maybe WCF) - that works fine within the same
The Definitive Guide to Windows Installer
"David Thielen" <thielen (AT) nospam (DOT) nospam> wrote
Re: Named pipes class for .NET - 09-29-2009 , 05:13 AM
Here are my answers to your questions:
1) What is the best way to perform IPC? This will always be on the
Named pipes and file mapping should work for your senario.
2) If it's named pipes, is there a link to a correct example of how to
do this from .NET? Preferably a very simple implementation as all we
need to do is get a byte value across.
Please refer to: http://msdn.microsoft.com/en-us/library/bb546085.aspx
It has a sample by using NamedPipeServerStream.
Or in CodeFx samples, please check CSNamedPipeClient / Server and
CSFileMappingClient / Server. Both samples uses interop.
Please let me know if they work for you.
Hongye Sun (hongyes (AT) online (DOT) microsoft.com, remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you.
This posting is provided "AS IS" with no warranties, and confers no rights.
|Thread Tools||Search this Thread|