Strong Name Assembly

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. Any ideas? Regards, Chris.Get .NET 2.0 SDK (FREE) for you dev box and try it again

--
Daniel Fisher(lennybacon)
http://www.lennybacon.com

"Chris" <123@.123.com> wrote in message
news:uZ6CKud7FHA.444@.TK2MSFTNGP11.phx.gbl...
>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. Any ideas? Regards, Chris.

Strong Name Assembly

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. Any ideas? Regards, Chris.Get .NET 2.0 SDK (FREE) for you dev box and try it again
Daniel Fisher(lennybacon)
http://www.lennybacon.com
"Chris" <123@.123.com> wrote in message
news:uZ6CKud7FHA.444@.TK2MSFTNGP11.phx.gbl...
>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. Any ideas? Regards, Chris.
>

Strong Naming a dll and registering in GAC

Hi,

I am working with Microsoft Configuration Application Blocks and whenever I
create a new app and have to use it, I have to reference it and it makes a
local copy in the bin directory.
so if i created 4 apps then there are local copies of these blocks...

I tried to use GACUtil to register these dlls but it gives me an error
saying that its not having a strong name, i tried sn tool but unsuccessful.
I have tried to strong name a dll but the way i did it was in an app where I
first created a strong name and then referenced it in the app before
compiling the dll and then used GAC to register it...
but this is some external dll...

I mean is my thought process right or I am totally off base...
Please advice,
Stephenstephen,
You cannot install an assembly in the GAC without a strong name so you need
to solve this problem first.
After that, you can put copies of strong named, GAC-ed assemblies in a
single folder and reference these from your various apps; you can turn off
the copy local feature, and the copy in the GAC will be automatically used.
Hope that helps,
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"stephen" wrote:

Quote:

Originally Posted by

>
Hi,
>
I am working with Microsoft Configuration Application Blocks and whenever I
create a new app and have to use it, I have to reference it and it makes a
local copy in the bin directory.
so if i created 4 apps then there are local copies of these blocks...
>
I tried to use GACUtil to register these dlls but it gives me an error
saying that its not having a strong name, i tried sn tool but unsuccessful.
I have tried to strong name a dll but the way i did it was in an app where I
first created a strong name and then referenced it in the app before
compiling the dll and then used GAC to register it...
but this is some external dll...
>
I mean is my thought process right or I am totally off base...
Please advice,
Stephen
>
>
>