Administrators Jon Posted June 17, 2011 Administrators Posted June 17, 2011 I've written a C# Windows Service and a C# program that runs in normal standard user mode. I need the user program to communicate with the service, then the service does something, and returns the result to the user program. I need to get a rough idea of the APIs/functions I need to research. It will just be local on a machine. I saw this: http://msdn.microsoft.com/en-us/library/system.servicemodel.netnamedpipebinding.aspx - is that on the right track?
Valik Posted June 17, 2011 Posted June 17, 2011 Named pipes are almost always the way to go with IPC. IIRC CreateProcessWithLogonW() uses pipes to communicate with the Secondary Logon service. Or something like that.
Administrators Jon Posted June 18, 2011 Author Administrators Posted June 18, 2011 There#s native classes in .NET 3.5 to do the named pipes stuff that look perfect for what I want. Cheers.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now