>NUnit includes their key for
>signing within the build source, but I tend to think we should use our
own
>key so that people can verify the source of the assembly.
I agree that if you rebuild, it should use the actual builder's key for
signing. Including the key with the source seems to defeat th
To provide some context on this, we are now using standard artifact
resolvers for .NET assemblies and require that the filename of an assembly
contain the version. This filename is also an attribute within the manifest
of the library assembly and needs to match the actual filename of the
artifact.
That depends on the answer to #1, below. If we don't need to re-sign the
assembly ourself, then we can simply deploy the framework assembly that
comes with their install. If we do want to re-sign, then we can re-assembly
it ourself.
Thanks,
Evan
On Jan 11, 2008 2:28 PM, Jason van Zyl <[EMAIL PR
Who created the NUnit assembly?
As is from them, or something you augmented?
On 11-Jan-08, at 11:34 AM, Evan Worley wrote:
Hello All,
If anyone can help on the questions below, it would be greatly
appreciated.
Thank you,
Evan
-- Forwarded message --
From: Evan Worley <[EM
