Game explorer - Revision history

Anders: Added/fixed links

2022-11-05T23:55:22Z

Added/fixed links

â† Older revision		Revision as of 23:55, 5 November 2022
Line 4:		Line 4:
	Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.		Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

	Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.		Before using this code, a game with an implemented GDF must already be prepared. GDF stands for [https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ee417681(v=vs.85) Game Definition File] and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

	== Code ==		== Code ==
Line 234:		Line 234:
	=== Additional Tasks ===		=== Additional Tasks ===

	'''GameExplorer_AddGame''' creates only one task by default - the ''Play'' task. To create more, a shortcut must be created in a numbered directory under ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\PlayTasks\<task number>'' or ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\SupportTasks\<task number>''. The ''Play'' task is numbered 0 under PlayTasks, so the next play task should be numbered 1, while the next support task should be numbered 0.		'''GameExplorer_AddGame''' creates only one [https://learn.microsoft.com/en-us/previous-versions/windows/desktop/legacy/ee417686(v=vs.85) task] by default - the ''Play'' task. To create more, a shortcut must be created in a numbered directory under ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\PlayTasks\<task number>'' or ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\SupportTasks\<task number>''. The ''Play'' task is numbered 0 under PlayTasks, so the next play task should be numbered 1, while the next support task should be numbered 0.

	<highlight-nsis>		<highlight-nsis>
Line 267:		Line 267:
	== Related MSDN Pages ==		== Related MSDN Pages ==

	*[http://msdn2.microsoft.com/en-us/library/bb206359.aspx#Integrating_into_an_Installer Integrating Windows Game Explorer into an Installer]		*[https://learn.microsoft.com/en-us/windows/win32/dxtecharts/windows-game-explorer-integration#http://msdn2.microsoft.com/en-us/library/bb206359.aspx#Integrating_into_an_Installer Integrating Windows Game Explorer into an Installer]
	*[http://msdn2.microsoft.com/en-us/library/bb173435.aspx Game Definition File Editor]		*[http://msdn2.microsoft.com/en-us/library/bb173435.aspx Game Definition File Editor]

Line 277:		Line 277:
	[[Games_Explorer_Manager_Install]] for the Games Explorer Manager		[[Games_Explorer_Manager_Install]] for the Games Explorer Manager

	[https://code.msdn.microsoft.com/GDF-Trace-5389d1b4/sourcecode?fileId=92718&pathId=490147704 ratings.xml] (GDF file must be signed)		[https://github.com/walbourn/directx-sdk-samples/blob/main/GDFTrace/ratings.xml#https://code.msdn.microsoft.com/GDF-Trace-5389d1b4/sourcecode?fileId=92718&pathId=490147704 ratings.xml] (GDF file must be signed)

	[https://code.msdn.microsoft.com/GameuxInstallHelper-6a9335ca#https://github.com/walbourn/directx-sdk-samples Gameux Install Helper (DX SDK)]		[https://code.msdn.microsoft.com/GameuxInstallHelper-6a9335ca#https://github.com/walbourn/directx-sdk-samples Gameux Install Helper (DX SDK)]

Anders: Added ratings.xml and gameuxhlpr links

2017-06-15T00:11:51Z

Added ratings.xml and gameuxhlpr links

â† Older revision		Revision as of 00:11, 15 June 2017
Line 276:		Line 276:

	[[Games_Explorer_Manager_Install]] for the Games Explorer Manager		[[Games_Explorer_Manager_Install]] for the Games Explorer Manager

			[https://code.msdn.microsoft.com/GDF-Trace-5389d1b4/sourcecode?fileId=92718&pathId=490147704 ratings.xml] (GDF file must be signed)

			[https://code.msdn.microsoft.com/GameuxInstallHelper-6a9335ca#https://github.com/walbourn/directx-sdk-samples Gameux Install Helper (DX SDK)]

			[https://github.com/iryoku/smaa/blob/master/Demo/DXUT/Core/DXUTmisc.cpp DXUTReLaunchMediaCenter]

	[[Category:Code Examples]]		[[Category:Code Examples]]

Anders: Per-user is under LocalAppData NOT AppData!

2017-06-14T12:03:12Z

Per-user is under LocalAppData NOT AppData!

â† Older revision		Revision as of 12:03, 14 June 2017
Line 105:		Line 105:

	SetShellVarContext all		SetShellVarContext all
			CreateDirectory $APPDATA\Microsoft\Windows\GameExplorer\$R2\PlayTasks\0
			CreateShortcut $APPDATA\Microsoft\Windows\GameExplorer\$R2\PlayTasks\0\Play.lnk $R3


	!else if ${CONTEXT} == user		!else if ${CONTEXT} == user

	SetShellVarContext current		SetShellVarContext current
			CreateDirectory $LocalAPPDATA\Microsoft\Windows\GameExplorer\$R2\PlayTasks\0
			CreateShortcut $LocalAPPDATA\Microsoft\Windows\GameExplorer\$R2\PlayTasks\0\Play.lnk $R3

	!endif		!endif

	~~CreateDirectory $APPDATA\Microsoft\Windows\GameExplorer\$R2\PlayTasks\0~~
	~~CreateShortcut $APPDATA\Microsoft\Windows\GameExplorer\$R2\PlayTasks\0\Play.lnk $R3~~

	${EndIf}		${EndIf}

Line 234:		Line 236:
	'''GameExplorer_AddGame''' creates only one task by default - the ''Play'' task. To create more, a shortcut must be created in a numbered directory under ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\PlayTasks\<task number>'' or ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\SupportTasks\<task number>''. The ''Play'' task is numbered 0 under PlayTasks, so the next play task should be numbered 1, while the next support task should be numbered 0.		'''GameExplorer_AddGame''' creates only one task by default - the ''Play'' task. To create more, a shortcut must be created in a numbered directory under ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\PlayTasks\<task number>'' or ''$APPDATA\Microsoft\Windows\GameExplorer\<instance GUID>\SupportTasks\<task number>''. The ''Play'' task is numbered 0 under PlayTasks, so the next play task should be numbered 1, while the next support task should be numbered 0.

	<highlight-nsis># restore instance GUID to $0 somehow		<highlight-nsis>
			SetShellVarContext all
			# restore instance GUID to $0 somehow
	CreateDirectory $APPDATA\Microsoft\Windows\GameExplorer\$0\PlayTasks\1		CreateDirectory $APPDATA\Microsoft\Windows\GameExplorer\$0\PlayTasks\1
	CreateShortcut "$APPDATA\Microsoft\Windows\GameExplorer\$0\PlayTasks\1\Network Play.lnk" \		CreateShortcut "$APPDATA\Microsoft\Windows\GameExplorer\$0\PlayTasks\1\Network Play.lnk" \

Kichik: Reverted edits by 178.212.31.2 to last version by 213.235.219.154

2011-04-21T20:02:52Z

Reverted edits by 178.212.31.2 to last version by 213.235.219.154

â† Older revision		Revision as of 20:02, 21 April 2011
Line 1:		Line 1:
	{{PageAuthor\|~~co[[File:Example.jpg]]dev~~}}		{{PageAuthor\|codev}}

	~~== Description ==~~
	Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

	Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

	== Description ==		== Description ==

178.212.31.2: /* Description */

2011-04-21T19:44:35Z

Description

â† Older revision		Revision as of 19:44, 21 April 2011
Line 6:		Line 6:
	Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.		Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

			== Description ==
			Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

			Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

	== Code ==		== Code ==

178.212.31.2 at 19:44, 21 April 2011

2011-04-21T19:44:26Z

â† Older revision		Revision as of 19:44, 21 April 2011
Line 1:		Line 1:
	{{PageAuthor\|~~codev~~}}		{{PageAuthor\|co[[File:Example.jpg]]dev}}

			== Description ==
			Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

			Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.


	== Code ==		== Code ==

178.212.31.2: /* Description */

2011-04-21T19:44:15Z

Description

â† Older revision		Revision as of 19:44, 21 April 2011
Line 1:		Line 1:
	{{PageAuthor\|codev}}		{{PageAuthor\|codev}}

	~~== Description ==~~
	Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

	Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

	== Code ==		== Code ==

178.212.31.2 at 19:44, 21 April 2011

2011-04-21T19:44:07Z

â† Older revision		Revision as of 19:44, 21 April 2011
Line 2:		Line 2:

	== Description ==		== Description ==
			Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

			Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

	== Code ==		== Code ==

178.212.31.2 at 19:43, 21 April 2011

2011-04-21T19:43:56Z

â† Older revision		Revision as of 19:43, 21 April 2011
Line 2:		Line 2:

	== Description ==		== Description ==
	Microsoft Windows Vista ships with a feature called Game Explorer that allows a developer to list games in a central explorer location. This page contains code that allows a NSIS installer to add and remove a game from the Game Explorer.

	Before using this code, a game with an implemented GDF must already be prepared. GDF stands for Game Definition File and is actually a XML embedded as a resource in the game executable. The resource type should be named DATA and the resource itself should be named __GDF_XML. For more information, see MSDN.

	== Code ==		== Code ==

213.235.219.154: /* Code */

2009-10-29T15:37:46Z

Code

â† Older revision		Revision as of 15:37, 29 October 2009
Line 108:		Line 108:
	!else if ${CONTEXT} == user		!else if ${CONTEXT} == user

	SetShellVarContext ~~user~~		SetShellVarContext current

	!endif		!endif