Delay signing

[Graham Allwood]

Hi,

I have an assemly that is delay signed during the dev work and then it is
resigned later when we perform a release build. In the same solution I have
a setup project that uses the PRIMARY OUTPUT of the first project. I also
have a new Configuration setting where I can just build the setup project.

Now, my problem is that the setup project seems to be recompiling the
primary output of the first project before it includes it. The problem is
that this new compile will not be fully signed.

How should I handle this? Do I have to stop using primary output setup group
and start pointing the project to the output assembly that has been
resignedy?

Thanks for any help

Graham Allwood

[Huihong Luo]

Perhaps, you can try one of the following

(1) If you are using VS.NET 2003, you can specfiy a command in the Build
Events of your project,
sn -R <assembly> <keyfile> when Build is success

This way, everytime when the build is successful, your primary output will
be resigned, and thus your setup project has the right version

(2) You must explicitly tell the setup project not to use the primary output
(as you guessed)
In setup project properties, "Exclude" the primary output, and add your
resigned assemblies into the project

Huihong
protect your .net code @ http://www.remotesoft.com

"Graham Allwood" <gr************@idesta.com> wrote in message
news:OD*************@tk2msftngp13.phx.gbl...

Hi,

I have an assemly that is delay signed during the dev work and then it is
resigned later when we perform a release build. In the same solution I have a setup project that uses the PRIMARY OUTPUT of the first project. I also
have a new Configuration setting where I can just build the setup project.

Now, my problem is that the setup project seems to be recompiling the
primary output of the first project before it includes it. The problem is
that this new compile will not be fully signed.

How should I handle this? Do I have to stop using primary output setup group and start pointing the project to the output assembly that has been
resignedy?

Thanks for any help

Graham Allwood

[Graham Allwood]

Thanks for the reply. It seems that 2) is the only way. I don't want to
fully sign my assemblies on the developers desktop so I can't really put
anything in the build events.

Cheers

Graham

"Huihong Luo" <hu******@stanfordalumni.org> wrote in message
news:uL**************@TK2MSFTNGP11.phx.gbl...

Perhaps, you can try one of the following

(1) If you are using VS.NET 2003, you can specfiy a command in the Build
Events of your project,
sn -R <assembly> <keyfile> when Build is success

This way, everytime when the build is successful, your primary output will
be resigned, and thus your setup project has the right version

(2) You must explicitly tell the setup project not to use the primary output (as you guessed)
In setup project properties, "Exclude" the primary output, and add your
resigned assemblies into the project

Huihong
protect your .net code @ http://www.remotesoft.com

"Graham Allwood" <gr************@idesta.com> wrote in message
news:OD*************@tk2msftngp13.phx.gbl...

Hi,

I have an assemly that is delay signed during the dev work and then it is resigned later when we perform a release build. In the same solution I

have

a setup project that uses the PRIMARY OUTPUT of the first project. I also have a new Configuration setting where I can just build the setup project.
Now, my problem is that the setup project seems to be recompiling the
primary output of the first project before it includes it. The problem is that this new compile will not be fully signed.

How should I handle this? Do I have to stop using primary output setup

group

and start pointing the project to the output assembly that has been
resignedy?

Thanks for any help

Graham Allwood