"Fabio R." <fabio71 _ at _ yahoo.it> wrote in message
news:OUGhji4TGHA.5972@TK2MSFTNGP10.phx.gbl...
> Hi all,
> what can I do to avoid that someone replace a dll of my asp.net project
> with another one?
> Example: in check.dll there's the method VerifyUrl to check if the current
> domain name is www.site.com, otherwise it return false.
> I don't want that someone replaces check.dll with another one with
> VerifyUrl that always return true...
> I'm not so expert, so probably I miss something...
> Thanks to anyone can help me,
> Fabio
>

"Fabio R." <fabio71 _ at _ yahoo.it> wrote in message
news:%23ZJGIt4TGHA.5900@tk2msftngp13.phx.gbl...
> So I need to sign with the same assemblykey all my dll...
> After this, the application stops to work if a dll is replaced with a
> disassembled one?
> Thansks,
> Fabio
>
> "Karl Seguin [MVP]" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME
> net> ha scritto nel messaggio
> news:OHzWSp4TGHA.1728@TK2MSFTNGP11.phx.gbl...
>> Sign your assembly (you'll need to sign all other assemblies that
>> reference it as well).
>>
>> You can generate a key by doing
>>
>> sn -k SomeKeyName.snk in a VS.NET command prompt
>>
>> You can then add the key to your project via the assemblyKeyFile
>> attribute:
>>
>> [assembly: AssemblyKeyFile("..\\..\\..\\SomeKeyName.key")]
>>
>> Here's some references:
>> http://blogs.msdn.com/junfeng/archive/2006/03/11/549355.aspx
>>
>> or simply google "assembly signing" or "assembly strong naming"
>>
>> Karl
>>
>>
>> --
>> http://www.openmymind.net/
>> http://www.fuelindustries.com/
>>
>>
>> "Fabio R." <fabio71 _ at _ yahoo.it> wrote in message
>> news:OUGhji4TGHA.5972@TK2MSFTNGP10.phx.gbl...
>>> Hi all,
>>> what can I do to avoid that someone replace a dll of my asp.net project
>>> with another one?
>>> Example: in check.dll there's the method VerifyUrl to check if the
>>> current domain name is www.site.com, otherwise it return false.
>>> I don't want that someone replaces check.dll with another one with
>>> VerifyUrl that always return true...
>>> I'm not so expert, so probably I miss something...
>>> Thanks to anyone can help me,
>>> Fabio
>>>
>>
>>
>
>

> Sign your assembly (you'll need to sign all other assemblies that
> reference it as well).
>
> You can generate a key by doing
>
> sn -k SomeKeyName.snk in a VS.NET command prompt
>
> You can then add the key to your project via the assemblyKeyFile
> attribute:
>
> [assembly: AssemblyKeyFile("..\\..\\..\\SomeKeyName.key")]
>
> Here's some references:
> http://blogs.msdn.com/junfeng/archive/2006/03/11/549355.aspx
>
> or simply google "assembly signing" or "assembly strong naming"
>
> Karl
>
>
> --
> http://www.openmymind.net/
> http://www.fuelindustries.com/
>
>
> "Fabio R." <fabio71 _ at _ yahoo.it> wrote in message
> news:OUGhji4TGHA.5972@TK2MSFTNGP10.phx.gbl...
>> Hi all,
>> what can I do to avoid that someone replace a dll of my asp.net project
>> with another one?
>> Example: in check.dll there's the method VerifyUrl to check if the
>> current domain name is www.site.com, otherwise it return false.
>> I don't want that someone replaces check.dll with another one with
>> VerifyUrl that always return true...
>> I'm not so expert, so probably I miss something...
>> Thanks to anyone can help me,
>> Fabio
>>
>
>