J
Jeff Ptak
Can anyone explain to me what I need to do to deploy a strong-named assembly
into the GAC? I have an assembly that I can deploy on its own into the GAC
using a Setup project. This works fine for a developer's machine.
However, when a developer makes a reference to the shared assy, it is copied
locally to the new project's output directory. Then when a setup project is
created for the new app, the shared assy ends up as a private assy instead
of being installed into the GAC on the target machine.
I have read in many places on the MSDN site about using the Windows
Installer 2.0 to "automatically" install strong-named assemblies into the
GAC. How do I set that up?
Thanks in advance!
into the GAC? I have an assembly that I can deploy on its own into the GAC
using a Setup project. This works fine for a developer's machine.
However, when a developer makes a reference to the shared assy, it is copied
locally to the new project's output directory. Then when a setup project is
created for the new app, the shared assy ends up as a private assy instead
of being installed into the GAC on the target machine.
I have read in many places on the MSDN site about using the Windows
Installer 2.0 to "automatically" install strong-named assemblies into the
GAC. How do I set that up?
Thanks in advance!