Based on everything I've read about WCF services using net pipes I expected to be able to use the address net.pipe://localhost/service/ on different user sessions as WCF does not use the name but a GUID.
基于我所读到的有关使用网络管道的WCF服务的所有内容，我希望能够在不同的用户会话上使用地址net.pipe：// localhost / service /，因为WCF不使用名称而是使用GUID。
Anyway when I launch several services I get a AddressAlreadyInUseException with the message:
无论如何，当我启动多个服务时，我得到一个带有消息的AddressAlreadyInUseException：
Cannot listen on pipe name 'net.pipe://localhost/service/' because another pipe endpoint is already listening on that name.
Is there a way to limit the scope of every WCF service to the user session? Connections will come always from the same user session.
有没有办法将每个WCF服务的范围限制为用户会话？连接将始终来自同一用户会话。
1 个解决方案
#1
4
What we have found is that Administrator users can see named piped between sessions while normal users do not see them. So we ended up running the application without admin rights and that was it.
我们发现管理员用户可以在会话之间看到命名管道，而普通用户看不到它们。所以我们最终运行没有管理员权限的应用程序就是这样。
What I don't know if this behavior is something that can be changed or if it is fixed in Windows.
我不知道这种行为是否可以改变或是否在Windows中得到修复。
#1
4
What we have found is that Administrator users can see named piped between sessions while normal users do not see them. So we ended up running the application without admin rights and that was it.
我们发现管理员用户可以在会话之间看到命名管道，而普通用户看不到它们。所以我们最终运行没有管理员权限的应用程序就是这样。
What I don't know if this behavior is something that can be changed or if it is fixed in Windows.
我不知道这种行为是否可以改变或是否在Windows中得到修复。