.NET Framework Deployment Features
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer

.NET Framework Deployment Features 

The .NET Framework provides a number of basic features that make it easier to deploy a variety of applications. These features include:

  • No-impact applications.

    This feature provides application isolation and eliminates DLL conflicts. By default, components do not affect other applications.

  • Private components by default.

    By default, components are deployed to the application directory and are visible only to the containing application.

  • Controlled code sharing.

    Code sharing requires you to explicitly make code available for sharing rather than being the default behavior.

  • Side-by-side versioning.

    Multiple versions of a component or application can coexist, you can choose which versions to use, and the common language runtime enforces versioning policy.

  • XCOPY deployment and replication.

    Self-described and self-contained components and applications can be deployed without registry entries or dependencies.

  • On-the-fly updates.

    Administrators can use hosts, such as ASP.NET, to update program DLLs, even on remote computers.

  • Integration with the Microsoft Windows Installer.

    Advertisement, publishing, repair, and install-on-demand are all available when deploying your application.

  • Enterprise deployment.

    This feature provides easy software distribution, including using Active Directory.

  • Downloading and caching.

    Incremental downloads keep downloads smaller, and components can be isolated for use only by the application for zero-impact deployment.

  • Partially trusted code.

    Identity is based on the code rather than the user, policy is set by the administrator, and no certificate dialog boxes appear.

See Also

© 2016 Microsoft