Re: Delayed Signing, the GAC, and Installations

From: Nicole Calinoiu (calinoiu)
Date: 11/10/04 

Date: Wed, 10 Nov 2004 10:00:08 -0500

"Bill" <nospam@devdex.com> wrote in message
news:%23wyasMzxEHA.3908@TK2MSFTNGP12.phx.gbl...
> Nicole,
>
> Thanks for your response. You brought up some good questions. The answer
> to your first one is yes, after delay-signing the assembly I am able to
> use gacutil to add it to the GAC.
>
> Your second question is making me wonder. To create the Setup project,
> I've add the "Primary Output" for the project that compiles to the
> signed assembly, which called ClassLibrary1 . Maybe the problem is that,
> when I build the Setup project, it rebuilds the ClassLibrary1 dll and it
> is no longer signed?

Yup.

> If that is the case, what is the process for
> delay-signing assemblies and including them in a Setup project?

Manually add the fully signed DLL to the setup project instead of adding it
as a project primary output. Instructions for adding a file to a setup
project can be found at
http://msdn.microsoft.com/library/en-us/vsintro7/html/vbconaddingitemstodeploymentproject.asp.
Once you remove your project output from the setup project contents, you
might also need to add back some other files (e.g.: images, application
configuration file, or other supporting files) from your DLL project if they
need to be included in the distribution package
.

>
> Thanks!
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Relevant Pages

  • RE: Custom Actions for web deployment projects
    ... This will include the dll which contains the xxxInstaller.cs ... This custom installer code is to be called from the setup project. ... However, in order to be referenced when setting up a custom action, the dll ... This duplicate file warning can be avoided by making the addition of the dll ...
    (microsoft.public.vsnet.general)
  • Re: VS2005 beta1 - setup project problems
    ... > I have multiple COM dll projects and a setup project in one solution. ... > Both build and installation on a clear machine run without errors, ... > MERGE_PROXYSTUB option and it registers interfaces. ...
    (microsoft.public.vsnet.setup)
  • VS2005 beta1 - setup project problems
    ... I have multiple COM dll projects and a setup project in one solution. ... Both build and installation on a clear machine run without errors, ... MERGE_PROXYSTUB option and it registers interfaces. ...
    (microsoft.public.vsnet.setup)
  • Re: Office COM add-in / setup project / deployment
    ... The main thing on the release version is the Strong name should be the same so if you adjust your setup project to include the release files from the Managed Code solution this should be fine. ... Additionally you can setup your development environment to use the SHIMMED version and is advised as a precaution the Managed Code addin will be using REGASM on rebuild/build of the solution which will knock out the shim on the dev machine only, you can goto properties of the ManagedCode project and untick regasm for this project to alieviate that. ... Since I knew that this DLL needed registered, ... I found a whole bunch of registry keys in the Registry section of the ...
    (microsoft.public.office.developer.com.add_ins)
  • Re: using dll from word
    ... A new setup project took care of the ... trouble. ... >The setup copies dll to program folder and registers the dll in the ... >In word I register the dll in my vba project (tick it in the register ...
    (microsoft.public.dotnet.languages.vb)
Quantcast