Strong names ...

[Leonardo D'Ippolito]

Hello sirs,

I am trying to understand how strong names work.

Suppose I have lib.dll (a .net library), and also MyApplication.e xe (a .NET
WinApp) . MyApplication uses lib.dll . Suppose someone decompiles lib.dll
and replaces code parts, and then recompiles again. When MyApplication.e xe
will load lib.dll the next time, will it detect that it is a different dll
if they have strong names?

How can I implement this procedure? If someone can give me an example I
would appreciate!

Thanks a lot!

[Patrik Löwendahl [C# MVP]]

Re: Strong names ...

Strong names is just a way to identify the assembly as a unique one and
partly to make sure that updates come from the same publisher. It has no
Authenticode capabilities.

If you changes your version number when you re-compile tough, that's another
issue. That will definatly tell your application it's a new dll.

--
Patrik Löwendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"

"Leonardo D'Ippolito" <leodippolito@t erra.com.br> wrote in message
news:e9r1ViHzEH A.1596@TK2MSFTN GP10.phx.gbl...[color=blue]
> Hello sirs,
>
> I am trying to understand how strong names work.
>
> Suppose I have lib.dll (a .net library), and also MyApplication.e xe (a
> .NET
> WinApp) . MyApplication uses lib.dll . Suppose someone decompiles lib.dll
> and replaces code parts, and then recompiles again. When MyApplication.e xe
> will load lib.dll the next time, will it detect that it is a different dll
> if they have strong names?
>
> How can I implement this procedure? If someone can give me an example I
> would appreciate!
>
> Thanks a lot!
>
>
>[/color]