Export (0) Print
Expand All
1 out of 12 rated this helpful - Rate this topic

Isolated Applications

Isolated applications are self-describing applications installed with manifests. Isolated applications can use both private assemblies and shared assemblies.

An application is considered fully isolated if all of its components are either shared side-by-side assemblies or private assemblies. It is called partially isolated if it uses some components that are not side-by-side assemblies. Note that if an application uses some components that are not side-by-side assemblies, or uses private assemblies, the application may be affected by the installation or removal of other applications on the system. For more information, see Side-by-side Assembly Sharing.

Developers are encouraged to design isolated applications and to update existing applications into isolated applications for the following reasons:

  • Isolated applications are more stable and reliably updated because they are unaffected by the installation, removal, or upgrading of other applications on the system.
  • Isolated applications can be designed so that they always run using the same assembly versions with which they were built and tested.
  • Isolated applications can use functionality provided by the side-by-side assemblies made available by Microsoft. For more information, see Supported Microsoft Side-by-side Assemblies.
  • Isolated applications are not tied to the shipping schedule of their side-by-side assemblies because applications and administrators can update the configuration after deployment without having to reinstall the application. This would not apply in the case where only one version of the assembly is being made available.
  • A fully isolated application may be installed by using the xcopy command. Windows Installer can also be used to install an isolated application without impact to the registry. For more information, see Installation of Win32 Assemblies.

In some cases, existing applications can be updated into an isolated application without having to rewrite the application code. An application manifest can be created that describes the application's dependencies on side-by-side assemblies. If the application uses components that are not side-by-side assemblies, these may be deployed as private assemblies. Note that the possibility of doing this with third-party components may depend on licensing because the component will need to be authored as an assembly. For example, by creating an application manifest and specifying a dependence on the side-by-side common controls (COMCTL32), an application running on Windows XP can take advantage of Windows theming. You should always test your application to ensure it is compatible with the new version of the COMCTL32 assembly.

It may not be possible to update every existing application into a fully isolated application. For example, some Windows File Protection (WFP) system assemblies are not available as side-by-side assemblies and cannot be installed with the application as a private assembly. It may be possible to partially isolate such applications by specifying side-by-side assembly dependencies for some of the application's assemblies in an application manifest.

 

 

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

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.