wcf
wcf copied to clipboard
dotnet
Add Support for WCF Discovery
Are there any plans to add System.ServiceModel.Discovery namespaces into this repo?
https://msdn.microsoft.com/en-us/library/system.servicemodel.discovery%28v=vs.110%29.aspx
https://msdn.microsoft.com/en-us/library/dd456782%28v=vs.110%29.aspx
I use these namespaces and find them to be very useful. I am sure it would be a welcome addition to this project.
Maybe there is some crossover with the AllJoyn project?
https://channel9.msdn.com/Blogs/Internet-of-Things-Blog/Step-By-Step-Building-AllJoyn-Universal-Windows-Apps-for-Windows-10-Public-Preview
Either way WCF Discovery will be more specific for WCF clients and maybe the WCF Discovery API could be extended to support AllJoyn for IoT type scenarios?
Thanks for the suggestion @systemsymbiosis . We are still working out the strategy for which parts of the full .NET Framework WCF should be made available in the GitHub repo. We're taking a data-driven approach to prioritize, and feedback like yours helps in that. We have not yet discussed Discovery, and yours is the first request so far. If other developers reading this also want Discovery, this is a good place to say so. We appreciate the pointers to AllJoyn too, and if will investigate further.
@systemsymbiosis just to make sure we understand, could you briefly articulate some of the scenarios where you would use this (e.g. mobile device discovering a service? mid-tier discovering a service?).
@roncain thanks for the reply and clarification about how the project is working. Needless to say I was very happy to hear that WCF is being opensourced. Thanks to all those who made it happen. Of course it was just a little disappointing that some namespaces I use are not out there yet. I hope they make it into the opensource version at some stage.
My current scenario is that I want to be able to discover services on the network from both a WPF client and a Windows Phone and/or a Windows Universal Client. I just need a quick way to find out what services are available on a local network and identify when they have left the network so that the client apps are aware of current state and notified accordingly.
I saw a presentation a Build recently where the presenter said that WCF was coming to Windows Universal. He did not specify exactly what API surface area. It was stated in the following presentation just after the 46 minute mark
Deep Dive into XAML and .NET Universal Windows App Development
The slide in question states
Universal Windows 10 apps will have the same base surface area as Windows 8.1 And yes, that means WCF works on Phone
Given my scenario when I saw that slide I was very happy and keen to try it out. Is there a greater WCF API Surface area exposed on the Windows Universal Platform than what is opensourced in WCF via this repository? If there is I am hoping that System.ServiceModel.Discovery is included on Windows Universal API
Finally, and I apologize for all the extra links! There was another Build session that seems relevant to this discussion
Discovering Windows 10 Devices Over Wi-Fi: DNS-SD API
All in all it seems that there is plenty of innovation and demand for these types of services from the developer community. From my perspective, since I am familiar with WCF, it would be nice if we could leverage our existing knowledge to innovate in this space.
Also, if this get's implemented, maybe it's also time to fix this issue: https://connect.microsoft.com/VisualStudio/feedback/details/782294/wcf-service-discvery-not-working-net-4-0
Thanks for the +1 and pointer to the Connect issue, @jogibear9988!
It'd be great data if you had specific scenarios you want to enable that are different from @systemsymbiosis to allow our triage group to appropriately prioritize this feature request.
Please accept my vote for making discovery available to UWP WCF clients. This would definitely support my case to use UWP because it would maintain the current value and investment in our current WCF services. Thank you.
While this is not available to UWP yet, I'd suggest to take a look at my workaround here.
Do this help you?
I need this now! Writing a Windows 10 IoT UWP app that needs to discover available services on the local network.
As I have mentioned above, I have developed a workaround for this issue. Take a look at my answer on StackOverflow, and let me know if it helps.
@iurifarenzena I saw your StackOverflow answer, but it's not really what I'm looking for. I have a WPF app running on Windows 10 that provides a service with a WS-Discovery endpoint. What I need is a full WS-Discovery client endpoint on Windows 10 IoT so I can discover the service running on Windows 10.
+1 vote for this feature. I need to discover onvif cameras so I need the System.ServiceModel.Discovery namespace in my app to use DiscoveryClient and UdpDiscoveryEndpoint.
Hi,
If anybody's interested, we have ported DiscoveryClientProtocol and dependencies from Mono and .NET Reference Source (MIT licensed):
https://github.com/mendix/ws-disco
