Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Specifying a Default Activation Context

When your application or component creates a new process, Windows searches for a default application manifest. Note that a manifest included as a resource in the application takes precedence over an external manifest. The default activation context is the first activation context that is active before any other activation context has been activated. This activation context is always active unless you activate other contexts. If you define ISOLATION_AWARE_ENABLED when you compile your application or component, calls like CoCreateInstance, LoadLibrary, and CreateWindow can perform automatic context management.

The loader allows an application to specify its default activation context by two methods. You can put the manifest file in the resources of the executable and the loader will find it. This is the same as putting the manifest file in the executable's resource table. You can place the manifest in a file named Myapp.exe.Manifest in the same directory as Myapp.exe, and the loader finds it while looking for Myapp.exe.

If you use none of these methods, the application starts with the system default activation context, which contains a minimal set of assemblies.

A better way of using automatic context management is by compiling your application with ISOLATION_AWARE_ENABLED defined. The recommended method is to set this on the compiler's command line for the entire project being built rather than being set in individual source files or headers. This makes most Win32 APIs aware of activation contexts and how to manage them. Instead of having to do your own activation context management, you simply need to place a manifest in your resource table at resource ID ISOLATIONAWARE_MANIFEST_RESOURCE_ID (numeric value 2), of type RT_MANIFEST (numeric value 24.) Functions such as CreateWindow, CoCreateInstance, and SendMessage then automatically activate this context before making the actual call.

Note that if you compile with ISOLATION_AWARE_ENABLED defined, you cannot also do your own activation context management. With ISOLATION_AWARE_ENABLED defined, Windows ignores any dynamic activation context creation your application may attempt to do between ActivateActCtx and CreateWindow calls. This means that when your application uses ISOLATION_AWARE_ENABLED you must make sure that the manifest contains a complete list of all assemblies that your component requires.

 

 

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.