blocks|key|1771121|text|仅对于本地，我们已经成功地使用了命名管道。避免了TCP的开销，并且几乎(至少对于.NET)与您可以获得的效率一样高，同时也有一个像样的API可用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1771122|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For local only, we have had success using Named Pipes. Avoids the overhead of TCP, and is pretty much (at least for .NET) as efficient as you can get while also having a decent API to work with.

blocks|key|1556099|text|由于您只能使用WCF2.0，因此.Net可能不是一个好的选择。您可以使用具有共享内存的.Net远程处理作为同一台计算机上的应用程序域之间的底层通信机制。使用这种方法，您可以轻松地将您的进程放在不同的机器上，并将共享内存协议替换为网络协议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1556100|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Since you are limited to .Net 2.0 WCF is perhaps not an option. You could use .Net remoting with shared memory as the underlying communication mechanism between app domains on the same machine. Using this approach you can easily put your processes on different machines and replace the shared memory protocol with a network protocol.

blocks|key|1556163|text|您最好的选择是使用WCF。您将能够在windows服务中创建服务宿主，并公开GUI应用程序可以使用的定义良好的接口。WCF将允许您通过命名管道进行通信，或者您可以选择任何其他通信协议，如TCP、HTTP等。使用WCF，您可以获得强大的工具支持和大量可用的信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1556164|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Your best bet is to use WCF. You will be able to create a service host in the windows service and expose a well defined interface that the GUI application can consume. WCF will let you communicate via named pipes if you choose, or you can choose any other communication protocal like TCP, HTTP, etc. Using WCF you get great tool support and lots of available information.

blocks|key|1556206|text|与windows服务通信的标准方法是使用服务控制代码。Windows服务可以接收从0到255的代码。0-127为系统预留。128到255可用于自定义命令。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1556207|如果您需要使用数据库、xml、文件、tcp、http等将复杂对象发送到服务，则除了用于发送重载配置、过程项等控制命令之外，还应使用此控制代码。|1556208|还有其他可用的功能，例如查询服务。请参阅Windows服务文档和api。|1556209|http://arcanecode.com/2007/05/30/windows-services-in-c-sending-commands-to-your-windows-service-part-7/|offset|length|1556210|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|2V|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@$H|U|I|V|1|W]]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|G]]]]

The standard method of communicating with a windows service is to use service control codes. Windows services can receive codes from 0 to 255. 0-127 is reserved for system. 128 to 255 can be used for custom commands.

If you need to send complex objects to the service use database, xml, file, tcp, http etc. Other than that for sending control commands like reload configuration, process items etc this control codes should be used. 

There are additional functionalities available such as querying the service. See Windows service documentation and api.

<a href="http://arcanecode.com/2007/05/30/windows-services-in-c-sending-commands-to-your-windows-service-part-7/" rel="nofollow noreferrer">http://arcanecode.com/2007/05/30/windows-services-in-c-sending-commands-to-your-windows-service-part-7/</a>

blocks|key|1556240|text|我想补充一下这个讨论。如果这是一种方法，请责备我--但是一个信号量(或多个信号量)不能用于基本的通信吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1556241|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'd like to add to this discussion. Please rebuke me if this is way out there - but couldn't a semaphore (or multiple semaphores) be used for rudimentary communication?

I've never had to do IPC on Windows before. Currently I'm developing a pair of programs, a standard GUI/CLI app and a windows service. The app has to tell the service what to do. So, assuming the communication is local only, what would be the best communication method for these two processes?

Where best is defined as more robust and less error prone, not the most performant nor the easiest to code.

Code examples will be very welcome, but aren't required :-)

Note I'm asking about what to use, a standard TCP socket, named pipes, or some other means of communication only.

Thanks!

Interprocess communication for Windows in C# (.NET 2.0)

数据库

Windows

我以前从来没有在Windows上做过IPC。目前我正在开发一对程序，一个标准的GUI/CLI应用程序和一个windows服务。应用程序必须告诉服务该做什么。那么，假设通信仅在本地进行，那么这两个进程的最佳通信方法是什么呢？其中最好的定义是更健壮，更不容易出错，不是最好的，也不是最容易编码的。代码示例将非常受欢迎，但不是...

问C# (.NET 2.0)中的进程间通信
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C# (.NET 2.0)中的进程间通信EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C# (.NET 2.0)中的进程间通信
EN