Hi Trevor,
Thanks for your reply.
When developing a delay-signed assembly, we need first add it to the skip
verification list before using this assembly. However, we needn't first
generated the assembly specially for adding to the strongname skip
verification list. Sn.exe support the input form "*, strongname" to add
all assemblies which signed with a certain public key to the list. Here
strongname should be specified as the string of hexadecimal digits
representing the tokenized form of the public key. See the -t and -T
options to display the public key token.
So the development steps might be:
1) sn -Vr *,<strongname>, if you have more than one public keys, you need
repeat this step to add them.
2) write your delay signed assembly with "Register for COM Interop" = true
3) debuging, if code change goto 2)
4) sign the assembly for release
5) sn -Vd *,<strongname>
6) release
In development cycle, you need keep this assembly in the skip verification
list, or you program might meet problem because of the assembly load
failure caused by the strongname validation failed. Since it is still in
the skip list, developers will still be able use the rebuild solution menu
option to do build operation. You may remove the assembly from the list
after it is fully signed.
Here is just some basic idea for this issue, if you still have problem on
it, please let me know more detail about your secenario. I'll look into it
and see if I could find some workaround.
Thanks!
Best regards,
Ying-Shen Yu [MSFT]
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, "online" should be removed before
sending.
