dimanche 22 avril 2012 15:30
I have an Application with WCF services, each one of them have netNamedPipe endpoint.
When I enable Auto-Start, the endpoints are not available (timeout).
When I disable Auto-Start, everything works fine.
I understand that Auto-Start uses named pipes to start services. But why does that conflict with regular named pipe endpoints?
How can I avoid thoses conflicts (and still can use both Auto-Start and named pipe endpoints)?
Toutes les réponses
samedi 28 avril 2012 04:42Modérateur
I think this is because with auto start the management of the endpoints uses the net named pipe binding. I tried to think through this scenario a couple times and was wondering if you could expose more than one base address from your service and then use one address for auto start requests and the other for regular service requests.
If you created a custom workflow service host you could be more selective in choosing which addresses are used for auto start management. The following sample gives you a starting point: http://code.msdn.microsoft.com/Windows-Workflow-6b4ffbe8.
If this answers your question, please use the "Answer" button to say so | Ben Cline
- Modifié Ben Cline1MVP, Moderator samedi 28 avril 2012 04:43
- Modifié Ben Cline1MVP, Moderator lundi 30 avril 2012 13:04
- Modifié Ben Cline1MVP, Moderator lundi 30 avril 2012 13:05
- Modifié Ben Cline1MVP, Moderator lundi 30 avril 2012 13:07
- Proposé comme réponse Ben Cline1MVP, Moderator jeudi 7 juin 2012 21:58