Application Does Not Load Locally Deployed Files from .Local Manifest (810316)


The information in this article applies to:

  • Microsoft Platform Software Development Kit (SDK) 1.0
  • Microsoft Windows XP Home Edition SP1
  • Microsoft Windows XP Professional SP1

SYMPTOMS

When an application is run on the Windows XP platform, the application may use resources as defined by the default Windows binding behavior -- instead of using local resources and DLLs as specified by the .local manifest that is deployed with the application.

CAUSE

On a Windows XP Service Pack 1 (SP1)-based system, if an application manifest is provided either by the application author or by using the Microsoft Application Compatibility database, the existence of the .local manifest is ignored. This means that the ".local" manifest deployed to the application directory will not be used to modify the default Windows binding behavior. The application manifest takes precedence, and any changes to the default Windows binding behavior will be based on what is specified in the application manifest.

If the application manifest refers to files that are deployed locally with the application, the application will bind to the application local version of the files instead of to the globally shared version. An application manifest may exist as a resource in the executable, as a stand-alone file installed alongside the application, or may be provided by Microsoft Application Compatibility database. If an application manifest is provided by Microsoft Application Compatibility database, it takes precedence over what is provided by the application.

RESOLUTION

Update your existing application manifest included with your application to reference the files that are deployed locally with the application. These are the files that you are expecting to load from the application folder by using .local manifest. See the Platform SDK for information about adding file information to the manifest.

For Component Object Model (COM) objects, include the COM classes, Type Libraries, and InterfaceProxyStub information in the application.

STATUS

This behavior is by design.

MORE INFORMATION

For more information about how to create and use manifests, visit the following Microsoft Web site:

http://msdn.microsoft.com/library/en-us/sbscs/setup/side_by_side_assemblies_reference.asp

Modification Type:MinorLast Reviewed:7/11/2005
Keywords:kbprb KB810316
©2004 Microsoft Corporation. All rights reserved.