Best Practices for Games on Windows XP, Windows Vista, Windows 7, and Windows 8 (Windows)This article provides technical requirements and best practices for games that run on Windows. We wrote these technical requirements and best practices primarily to cover Windows Vista and Windows 7, as well as the legacy Windows XP operating system. These best practices also generally apply to desktop Win. Windows 8. This articles contains these sections: Differences for Windows 8. Here is a summary of the key differences when applying these technical requirements and best practices to Windows 8. The Games Explorer UI is not visible. All games that you register with the Games Explorer are surfaced as tiles in new Windows UI, but much of the metadata that is associated with the title is no longer visible. · Install Steam login | language Store Page. STAR WARS™ Republic Commando. All Discussions Screenshots Broadcasts Videos News. · There are two ways to install a strong-named assembly into the global assembly cache. with the file name hello.dll into the global assembly cache. Add dll to gac with the help of.NET Framework SDK V2.0/V4.0,or with the help of 'GACUTIL'.let's see how to install DLL in GAC (deploy DLL in GAC). Log into Facebook to start sharing and connecting with your friends, family, and people you know. You still use the Games Definition File Maker tool (GDFMAKER. EXE), which is now available in the Windows Software Development Kit (SDK), to author the metadata. You also use the existing mechanisms for deploying the metadata. Continue to test your Games Explorer registration by using Windows 7, and verify that the new Windows UI tile shows up when you install it on Windows 8 (see 1. Games Explorer Integration). To download the Windows 8 SDK, see Downloads for developing desktop apps. Registration with the Game Explorer APIs continues to be the mechanism for registering your game with Windows Parental Controls. We recommend that you run the Windows SDK version of GDFMAKER on the released version of Windows 8 to ensure that it can populate all currently supported rating systems. Note This version of GDFMAKER requires . NET 4. 0. See 1. 2 Support Family Safety / Parental Controls. There are now three choices for using the XINPUT API depending on your requirements. XINPUT 1. 4 is built into Windows 8. Both Windows Store apps and desktop Win. XINPUT 1. 4. All versions of Windows can use XINPUT 9. XINPUT 9. 1. 0. All versions of Windows can also use the existing Direct. X SDK version XINPUT 1. · Use of an ‘autorunner’ or other pre-install technology. or a DLL) as a resource. should review the full Games for Windows technical requirements. Great American Country brings you all things Americana, from shabby chic decorating for home or wedding to southern comfort food and travel tips across the U.S. En effet c'est bien une install pas réussie du pilote Blue Tooth de ma clé USB qui était en cause. J'ai eu aussi ce pb de btrez.dll-french. Direct. Setup to deploy. See 1. 4 Support the Xbox 3. Common Controller for Windows. Only a limited set of desktop Win. Windows RTGames that run on Windows 7 can and should run correctly on Windows 8 x. Dll File InstallerSee 2. 2 Support Windows x. Versions. Ensure any OS checks are done correctly. The Windows 8 OS version is “6. Windows 8 passes the current ‘minimum bar’ tests that we recommend for game deployment. The “Direct. X End- User Redistribution” package runs successfully on Windows 8, as it does on Windows 7, to deploy D3. DX9, D3. DX1. 0, D3. DX1. 1, XINPUT 1. XAUDIO 2. 7, XACTEngine, and so on. But, a known issue exists with Direct. Setup on systems with only . NET 4. 0 installed due to the deployment handling of the legacy Managed Direct. X 1. 1 assemblies. This issue applies to both Windows 8, which comes with . NET 4. 5 by default, and ‘fresh’ Windows XP computers with the . NET 4. 0 runtime installed. But, this issue does not apply to any version of . NET prior to . NET 4. While Windows 8 has an application compatibility behavior to resolve this issue automatically (which requires network access), we recommend that games that continue to deploy Direct. Setup update to the Direct. X SDK (June 2. 01. REDIST files. As always, if you use Direct. Setup for your title, trim your title down to the minimum required set of CABs. See 3. 4 Install Windows Resources Properly. Games that require the . NET “2. 0” compatible runtime (2. These games trigger an application compatibility behavior on Windows 8 to enable the . NET 3. 5 runtime automatically (which requires network access). But, we recommend that . NET developers move to the . NET 4. 0 runtime. Note The legacy Managed Direct. X 1. 1 assemblies are not compatible with the . NET 4. x runtime. See 3. 4 Install Windows Resources Properly. Use of an ‘autorunner’ or other pre- install technology that relies on . NET is not recommended. You can assume that only . NET 2. 0 compatible runtimes (2. Windows Vista and Windows 7. Only the . NET 4. Windows 8 by default. See 3. 7 Support Autorun. There is an updated Application Verifier for Windows 8. The Windows 8 SDK includes this updated Application Verifier. See 4. 2 Eliminate Application Verifier Failures. Additional Information. Windows 8 and Windows Server 2. Where is the Direct. X SDK? Games for Windows. Summary of Games Requirements. Customer Benefits. Computer games are a key entertainment experience on Windows, but ease- of- use concerns have caused customer frustration over the years. Traditionally, games are installed like applications, but they are utilized more like entertainment media (movies or songs, for example). Innovations, such as Games Explorer, expose games in a consistent manner that is different from standard applications. These innovations also give games first- class citizen status in Windows, together with Music and Pictures. The following requirements help ensure that Windows Vista and Windows 7 provide an improved, more accessible, and unified gaming experience. At the same time, they ensure compatibility with Windows XP. Games Explorer Integration. Requirement. The game must be visible within Games Explorer (the Games folder) on Windows Vista and Windows 7. When selected, the game must also display correct meta data, which includes publisher, developer, release date, version, Windows Experience Index scores, rating (if applicable), and associated hyperlinks. If the game is digitally distributed through an online game service, then the service provider should also appear in Games Explorer. To ensure proper handling of the provider and to enable use of RSS feeds, version 2 of the schema for game definition files (GDFs) should be used. For more information about GDFs, see Additional Information.). In addition, game installers must observe the following rules when they run on Windows Vista and Windows 7. The installation must not create a shortcut to launch the game on the desktop, in the Start menu, or in any other location. Tasks and shortcuts for removal must not be created. Users must be able to remove the game by using Programs and Features in Control Panel on Windows Vista and Windows 7, or Add or Remove Programs in Control Panel on Windows XP. On Windows XP, and on previous versions of Windows, the game installer is free to create program groups, desktop icons, or shortcuts as needed. Rationale. Windows Games Explorer is similar in concept to the Windows XP folders My Documents or My Pictures. The idea is to centralize similar content in one place and allow for easier organization and context- sensitive activities. Games Explorer extends the My Documents or My Pictures concept by allowing richer organization and control over games. Games Explorer allows gamers to view, organize, and interact with all the games installed on their systems. It also allows game publishers to communicate important game information more effectively. The system is data- driven, making it easy for a game publisher to update game information over the life of the product. Additional Information. Integration with Games Explorer requires that you author a game definition file (GDF), which is an XML text file that is embedded within a binary file (an executable file or a DLL) as a resource, along with a Windows icon. The game must then be registered with Games Explorer. The GDF also enables the exposure of supplied information such as the game title, publisher, developer, links to websites and optional tasks. Note that support tasks can be only links to Web sites, but play tasks can be used for optional support tasks as well. Games Explorer can make use of a thumbnail bitmap image, but it is recommended that, instead, you provide a Windows icon resource with large icons (2. The icon resource should include image sizes of 2. True Color) and 8- bit (2. The icon editor provided in Visual Studio 2. Icon. Workshop Lite. Details on integrating with Windows Games Explorer are provided in the Direct. X SDK. The Direct. GACThis content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |