Share via

Namespace Provider Installation (Windows Embedded CE 6.0)

  • Article

1/6/2010

The installation application for a namespace provider must call WSCInstallNameSpace to register with Ws2.dll and supply static configuration information. Ws2.dll uses this information to accomplish its routing function and in its implementation of WSAEnumNameSpaceProviders.

The results of these three operations are not visible to applications that are currently loaded and running. Only applications that begin executing after these operations have occurred will be affected by them.

This architecture explicitly supports the instantiation of multiple namespace providers within a single DLL, however each such provider must have a unique namespace provider identifier (GUID) allocated, and a separate call to WSCInstallNameSpace must occur for each instantiation. Such a provider can determine which instantiation is being invoked because the namespace provider (NSP) identifier appears as a parameter in every NSP function.

See Also

Concepts

Winsock Service Provider Interface (SPI)
Namespace Provider Initialization and Cleanup
Service Installation in the Winsock SPI
Service Query
Name Resolution Data Structures in the SPI
Compatible Name Resolution for TCP/IP in the Windows Sockets 1.1 SPI