cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Reureu
Level 10

Installing shared assemblies to the GAC

Hi,

I am working on a Basic MSI project and I am currently playing around with the GAC.


  • I have 1 InstallShield project that produces 2 releases (ReleaseA and ReleaseB) for 2 different product (ProductA and ProductB).
  • I have split 2 release specific features, and one common feature

    • FeatureA (ReleaseFlag: ReleaseA)
    • FeatureB (ReleaseFlag: ReleaseB)
    • FeatureCommon (No ReleaseFlag)

  • I have one .NET assembly that is shared by the 2 products.
It looks like a typical scenario for an assembly installation to the GAC.

Here are my questions:

  • Shall I make only 1 component, and include it in FeatureCommon? Or shall I make 2 components (ComponentA and ComponentB), and assign them to FeatureA and FeatureB respectively?
  • If I make 2 components, shall they have the same Component Code?
  • Shall I set the component as "Shared", or will the GAC handle the reference counting by itself?


Thanks in advance for your help!
Regards
Labels (1)
0 Kudos
(1) Reply
MSIYER
Level 8

Please make sure your assemblies are strongly named. That is the essential part.

•Shall I make only 1 component, and include it in FeatureCommon? Or shall I make 2 components (ComponentA and ComponentB), and assign them to FeatureA and FeatureB respectively?

Because the products share the assembly, I would have included it in the FeatureCommon.

•If I make 2 components, shall they have the same Component Code?

Yes.

•Shall I set the component as "Shared", or will the GAC handle the reference counting by itself?

You do not have to mark it as shared. GAC handles the sharing part.
0 Kudos