Signing Assemblies

[Steve]

Using VS .Net 2003

1. I'm confused on how to remove compile errors below.
Not sure if I need/how to use Al.exe and Gacutil.exe tools
with VS, etc.

2. My company doesn't have a private key and the local
windows application I'm creating is for internal company
network use only. Should I create a public key?

3. My goal is to compile a Release version of the
application to the network and then use caspol tool to
trust assembly. Make Sense?

Steps:
(a) Created key pair (sn -k foo.snk) and copied foo.snk
to C# project \obj directory (is my next step: sn -p
foo.snk fooPub.snk & AssemblyDelaySign(true) &
AssemblyKeyFile (fooPub.snk) ???)

(b) Changed AssemblyInfo.cs contents:
[assembly: AssemblyDelaySign(false)]
[assembly: AssemblyKeyFile(@"C:\...\obj\foo.snk")]
[assembly: AssemblyKeyName("")]

(c) Resulting compile errors (2):
Assbly gen. failed -- Ref assbly 'Interop.Word'
& 'Interop.Excel' no strong name

Thanks - Steve

 

[Mattias Sjögren]

(c) Resulting compile errors (2):

Assbly gen. failed -- Ref assbly 'Interop.Word'
& 'Interop.Excel' no strong name

Download the Office PIAs from Microsoft (they already have a strong
name) or create your own strong named interop assemblies with
Tlbimp.exe /keyfile.



Mattias