WCF Named Pipes timeout in a WinApp, but not in a ConsoleApp?
问题 In relation to Async two-way communication with Windows Named Pipes (.Net) which seems dead (the thread that is) :/ I'm wondering why the following code works perfectly in a ConsoleApplications, but when I do exactly the same thing with WindowsApplications I get an timeout on the client when calling "Console.WriteLine(proxy.ProcessData());". The strange thing is that the server method "ProcessData" is called without any exceptions, but still I get a timeout after the default 1 min?! How can I