Registering Lobby-Aware Applications
To enable a lobby to launch a DirectPlay application, the application must add the following entries to the system registry. Once an application has been registered, it will be recognized as a lobby-aware application and lobbies can launch it. These registry entries must be deleted when the application is removed.
The following example shows the registry entries for the DPCHAT sample application included in the SDK.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay\Applications\DPChat]
"Guid"="{5BFDB060-06A4-11D0-9C4F-00A0C905425E}"
"File"="dpchat.exe"
"CommandLine"=""
"Path"="C:\DXSDK\sdk\bin"
"CurrentDirectory"="C:\DXSDK\sdk\bin"
The keys and values are:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay\Applications\
The key's name will be the name of the application that the IDirectPlayLobby2::EnumLocalApplications method returns. It is DPChat in the preceding example.
Guid
This is the 16-byte GUID that identifies the application. It is formatted as shown in the example. This should be the same GUID that is put in the guidApplication member of the DPSESSIONDESC2 structure when creating a session. A globally unique identifier (GUID) can be generated using the Guidgen.exe utility.
File
This is the file name of the application executable.
CommandLine
This lists any command-line parameters that are to be specified when a lobby launches the application.
Path
This is the directory that the application executable resides in.
CurrentDirectory
This is the directory to set as the current directory after launching the application executable.