![]() ![]() When you prepare an installation package for your application, you must include information about the product's operating system version requirements. See Modifying the Registry, Registry Tables Group, Registry Table, RemoveRegistry Table, WriteRegistryValues Action, RemoveRegistryValues Action, Uninstall Registry Key, Properties, File Table, Directory Table, Using the Directory Table, IniFile Table, RemoveIniFile Table, IniLocator Table, WriteIniValues Action, RemoveIniValues Action, RemoveIniFile Table.ġ.7 The application should perform Windows version checking correctly. ini files, by using Windows Installer to install your application. ini file, as well as add or remove information from existing. You can easily manage the installation of a private. If your application uses information that you do not want to put in the registry, create a private initialization file and place it in the directory with the application's executable files. You can author the package for your application such that it is easy to check and set the values of these keys. When your application uses the installer, these registry keys become available as installer properties. Windows Installer supports informational keys in the registry. Your installation program should add entries to the registry not to the Win.ini, System.ini, Autoexec.bat or Config.sys. See Filename, File Table, Directory Table, SHORTFILENAMES Property.ġ.5 The application should not read from or write to Win.ini, System.ini, Autoexec.bat or Config.sys. The installer supports installing to and from both UNC and drive network and always uses the long file names provided in your package except if the SHORTFILENAMES Property is set or if the target volume does not support long file names. See Resiliency Overview of Windows Installer Roadmap to Windows Installer Documentation.ġ.3 Application should support Long File Names and UNC paths Using the Installer can improve the functionality and stability of your application. If you provide an installation package, your application can use the installer service available on all 32-bit Windows platforms. Requirement for Certificationġ.1 Application should perform primary functionality and maintain stability. Note that the not every requirement for certification discussed in the Application Specification is dependent upon Windows Installer. The following table provides links to information in Windows Installer documentation pertinent for some of the certification requirements. If you are authoring an installation package for your application, you may take advantage of the capabilities of the Microsoft Windows Installer to help satisfy several of the requirements for certification. Software vendors who comply with the specification qualify for the Certified for Microsoft Windows logo and then license the logo for use on their product packaging, advertising, collateral, and other marketing materials.įor more information about Windows Vista, Windows XP, and Windows Server 2008 certification for your applications, see the Microsoft Partner Network. This specification was developed by Microsoft in cooperation with customers and other developers to provide a road map for building reliable and manageable applications. The Certified for Microsoft Windows Logo identifies products that have been verified through independent testing to comply with the Application Specification for Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |