Installing to the GAC

I have a strong named assembly. It installs fine on my XP Pro Machine via
the .net configuration tool. When I use the same tool to install it on a
W2003 machine it says it isn't strongly named.
As I don't have vs.net. Ihave been compliling my vb file as a module and
then using al.exe to sign it with a strong name. It seems to work on my
machine. When I copy the dll to the 2003 machine it doesn't. Does it need
any additional files than the dll. Also the W2003 machine is .net v2 whereas
my machine is .net v1. The 2003 machine is a brand new installation of 2003,
which I don't know much about other than it is 'locked down'. Could there be
some kind of permissions issue?


Any ideas? Regards, Chris.

v-yren
Mon Nov 21 03:43:07 CST 2005

Hi Chris,

Welcome to Microsoft newsgroup!

Based on my understanding, your problem is that when adding the assembly by
using the .net configuration tool, the ¡°un-strongly named¡± warning
displayed. If I misunderstand anything, please let me know.

Based your description, I did the same test. I wrote a simple .cs file and
compiled it to .netmodule. After the compiling succeeded, I use sn.exe to
generate the key file and use the al.exe to link them to the assembly. Then
I add the assembly by using the .net configuration tool (v1.1)
successfully. I also copy the assembly to the Windows 2003 server and add
the assembly by using the .net configuration tool (v2.0), it also seems
successful.

For the current issue, my opinion is that there may be some particular
reason which causes your assembly isn¡¯t properly strong named. I¡¯d
suggest you use ¡°ILDasm /Adv xxx.dll¡± command to look into the assembly
for details. If the assembly has been correctly strong named, the
¡°.publickey = {xxxx¡­.}¡± will be displayed under the MANIFEST node. So
please check it first.

I hope the suggestions will be helpful. If you have any concerns, please
feel free to let me know. I¡¯m looking forward to your reply!

Regards,

Yuan Ren [MSFT]
Microsoft Online Support