INFO: Check for Windows Components Before Installation (225080)

This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location from which you downloaded the release.

SUMMARY

Your application's Setup program should check for the correct versions and locations of all required Windows components before installation. The Windows Installer and File Installation API functions help provide a standard way to organize and manage application files and components.

MORE INFORMATION

Windows 2000 includes upgraded components, such as DirectX and TAPI, from previous versions of both Windows 9x and Windows NT. It is not safe to assume that the files that make up these components will always be in any specific directory or folder. Setup programs that hard-code these paths will break if the user's system is configured differently than expected.

Note that it is also not safe to assume that related components will co-exist on a machine. You should check for each component that your application requires individually.

The Windows registry is the only reliable source of information for the location of all Windows components. The Windows Installer and the File Installation API functions provide a consistent, reliable way to extract this information from the registry and determine where these components currently exist or should be installed.

REFERENCES

For more information about the Windows Installer and the File Installation API functions, see the Windows Installer and Installing Applications sections under Management Services in the Platform SDK.