Title: Strong Names - Delay Signing - Relative Paths

Hello,

        Is anyone out there actually signing assemblies?  I am working through automating this with NAnt.  Of course, I want the process to actually sign the assemblies when run on our build server, but only partially sign (with public key only) when built on a developer's workstation.  Also, I want the solution to build with both NAnt and Visual Studio.  I figured key containers would simplify this.  However, I have not been able to install just the public key into a container.  So, I am back to key files for the developer builds.  Unfortunately, if I set the relative path in the KeyFile attribute to work from VS, the build fails from NAnt.  I am using the <solution> task to build the solution.  Could this be a bug in the solution task?

Thanks,
Tom

Reply via email to