WSDAPI for .NET
3/21/2011
This package is a Feature Pack in the category Embedded Enabling Features. The name of the package as it appears on disk and for use with some command-line tools is WinEmb-WSDAPI-NET. This package provides a managed code API for a network stack implementing the Device Profile for Web Services (DPWS) specification.
Settings
No settings provided.
Services
No services provided.
Dependencies
Package Dependencies
This package depends upon features provided by the following packages:
- .NET Framework 2.0
- Credentials and Certificate Management
- Remote Access Service
- Windows Management Instrumentation
Group Dependencies
No group dependencies.
Optional Supporting Packages
No optional supporting packages.
Common Uses
The DPWS specification defines discovery, metadata exchange, exchange of one-way and two-way messages, and eventing. It is an XML-based network protocol and can be used as UPnP alternative.
Notes
Ports and HTTPS
If you want to use HTTPS transport, you must add a valid SSL certificate to the certificate store and bind it to port 5358. If you want to use IPv4 and IPv6, you must bind a certificate to 0.0.0.0:5358 and [::]:5358.
A device running a service must allow incoming connections for port 3702 (UDP) and 5357 (TCP) for HTTP transport or 5358 (TCP) for HTTPS transport to the service assembly. The TCP ports can vary based on the implementation of the device. A device running a client must allow connections for the port and 5357 (TCP) for HTTP transport or 5358 (TCP) for HTTPS transport. Depending on the implementation of the client, a separate TCP port for eventing may be necessary.
Interoperability With Embedded Enabling Features
If you add SSL certificates are added to the certificate store and bound to the port after EWF is enabled, the ability to use HTTPS transport will not be persistent.
Security
Adding a certificate to the store and binding it to the port requires administrator privileges. This is only relevant, if you want to use HTTPS transport.
If the firewall is active and the firewall settings are not made in the deployment, setting up the firewall requires administrator privileges.