Re: Delayed Signing, the GAC, and Installations
From: Todd Derksen [MSFT] (tderksen_at_online.microsoft.com)
Date: Thu, 11 Nov 2004 19:22:26 GMT
Hopefully I can offer a little help on the delay sign issue mentioned
What is happening is that Visual studio detects the file has changed since
it built it (the signing of it)
What you can do to use project output is do the signing in the post build
event of the C# dll, this will cause it to build every time you build teh
setup project however it will be signed before it is included in the setup
Visual Basic Deployment Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
>From: Bill <firstname.lastname@example.org>
>Here is the article that got me interested in the smartcard usage:
>Basically, it says that using sn.exe to create the keypair on a
>hard-drive could expose you to malicious attempts to find the private
>key, even after you delete the pair. But if you generate the keys on a
>smart-card and safely store it in the company safe, you can ensure that
>nobody will be able to remotely find your private key.
>I'll pose my setup question to the setup newsgroup. Thanks for helping
>me out, you've helped a lot.
>*** Sent via Developersdex http://www.developersdex.com ***
>Don't just participate in USENET...get rewarded for it!