Determining the Best Site for Product Assembly: Tips & Strategies

Table of Contents

• Introduction
• Registration
• Using Advanced Installer
  • GUI
  • Working with Projects
  • Installer Project
    * Product Information
    * Resources
    * Files and Folders
    * Tiles
    * Java Products
    * Registry
    * File Associations
    * Assemblies
    * Assembly Properties
    * Assembly Destination
    * Drivers
    * Services
    * Package Definition
    * Requirements
    * User Interface
    * System Changes
    * Server
    * Custom Behavior
  • Patch Project
  • Merge Module Project
  • Updates Configuration Project
  • Windows Store App Project
  • Modification Package Project
  • Optional Package Project
  • Windows Mobile CAB Projects
  • Visual Studio Extension Project
  • Software Installer Wizards - Advanced Installer
  • Visual Studio integration
  • Alternative to AdminStudio/Wise
  • Replace Wise
  • Migrating from Visual Studio Installer
  • Keyboard Shortcuts
  • Shell Integration
  • Command Line
  • Advanced Installer PowerShell Automation Interfaces
• Features and Functionality
• Tutorials
• Samples
• How-tos
• FAQs
• Windows Installer
• Deployment Technologies
• IT Pro
• MSIX
• Video Tutorials
• Advanced Installer Blog
• Table of Contents

Disclaimer: This post includes affiliate links

If you click on a link and make a purchase, I may receive a commission at no extra cost to you.

Select Assembly Destination

Destination

Install in Global Assemblies Cache

By using this option, all the selected assemblies will be installed into the global assembly cache using the Microsoft .NET Framework. When installing assemblies to the global assembly cache, the installer cannot use the same directory structure and file version rules it uses when installing regular components. Assemblies can exist only once in the assembly cache. Each assembly is added and removed from the assembly cache as an indivisible whole. Because of this, all the files from an assembly are always installed or removed together.

Install to a private location (given by assembly file component directory)

Using this option will install the selected assemblies as private. A private assembly is used only by a single application and is stored in that application’s installation folder. The name of a private assembly name must be unique within the application that uses it. Windows Installer will take the file entry, look up the component that owns it and then use the directory entry associated with that component to install the private assembly to that same directory.

Did you find this page useful?

Please give it a rating:

Thanks!

Report a problem on this page

Information is incorrect or missing

Information is unclear or confusing

Something else

Can you tell us what’s wrong?

Send message

Also read: