3 ms·
Have you shipped anything using that API? I'm just a bit weary of wasting time on another half-baked solution. And are you sure the Windns.h API is deprecated?
by goont 6y ago
Have you shipped anything using that API? I'm just a bit weary of wasting time on another half-baked solution.
And are you sure the Windns.h API is deprecated? I could have sworn it only showed up last year.
- Fredej 6y agoI'm in the process of doing so. We had some issues with it initially but it seemed that it got better since a couple of updates ago. I vastly prefer it to having to ship mdnsresponder alongside my application though. I'm basing my "deprecated" comment on this: https://docs.microsoft.com/en-us/uwp/api/Windows.Networking.ServiceDiscovery.Dnssd?redirectedfrom=MSDN&view=winrt-19041 https://docs.microsoft.com/en-us/uwp/api/Windows.Networking.... However that looks to be different from the windns.h stuff. To be honest, I wasn't aware of windns.h and just assumed it was the above link you were talking about. It's probably worth taking a look at :)
- goont 6y ago> I vastly prefer it to having to ship mdnsresponder alongside my application though. That's what I'm seeking to avoid too. I'll have to take a closer look at the device enumeration API next time I circle around to the Windows port. Thanks for sharing your experience with it.