Microsoft Game Development Kit (GDK) preferred local User Datagram Protocol (UDP) multiplayer port API On resume, you should again wait for network initialization before calling WSAStartup and creating any new sockets. On suspend, you should close all socket handles and call WSACleanup. You should register for suspend and resume events via RegisterAppStateChangeNotification. For details about how to determine when the networking stack is ready, see Network initialization and connectivity. If WSAStartup is called too early during the title's launch process, WSAStartup or subsequent Winsock calls might fail.

Network initializationīefore making the first call to WSAStartup, Microsoft Game Development Kit (GDK) titles must ensure that the networking stack is ready. Only the APIs under the WINAPI_PARTITION_GAMES API family work in Microsoft Game Development Kit (GDK) titles. For Xbox console titles, you must link against XGamePlatform.lib, instead of directly against Winhttp.lib.For PC titles, continue to link against Winhttp.lib.lib files you need to include when using Winsock APIs. This topic describes the minor differences and best practices specific to the use of Winsock in Microsoft Game Development Kit (GDK) titles. The way Microsoft Game Development Kit (GDK) titles interact with Winsock is, generally the same as the way Win32 programs interact with Winsock. Windows Sockets 2 (Winsock) enables you to create advanced Internet, intranet, and other network-capable applications to transmit application data across the wire, independent of the network protocol being used. The Microsoft Game Development Kit (GDK) supports the use of the Windows Sockets 2

Winsock packet editor