Re: Dotfuscator problem
- From: "GaryDean" <GaryDean@xxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Aug 2007 10:19:54 -0700
Well, I guess I don't know how to obfuscate a dll that is signed. I was
hoping to get some guidance on that here on this forum.
G
"Peter Bromberg [C# MVP]" <pbromberg@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:9269481E-4118-4859-8D24-F62355794DDA@xxxxxxxxxxxxxxxx
Sounds to me like your original reference was to a strong-named assembly
which you obfuscated, losing the strong name signature and version info,
and
that you still expect the old reference to "work".
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com
"GaryDean" wrote:
Has anyone had success with this community edition obfuscator that comes
with vs2005? I put a dll through it and then when I substitute the
obfuscated dll for the original I get an error at compile time saying:
Error 1 Could not load file or assembly 'GP2, Version=0.2.0.0,
Culture=neutral, PublicKeyToken=21f9ec8df0a8817f' or one of its
dependencies. Strong name signature could not be verified. The assembly
may
have been tampered with, or it was delay signed but not fully signed with
the correct private key. (Exception from HRESULT: 0x80131045)
There is no support for this "software" that I am aware of.
Does anyone know of an affordable obfuscator that works?
--
Regards,
Gary Blakely
.
- References:
- Dotfuscator problem
- From: GaryDean
- Dotfuscator problem
- Prev by Date: Re: Querystring not working
- Next by Date: Re: Slightly OT: Resume Advice
- Previous by thread: Dotfuscator problem
- Next by thread: RE: Can't log in user having "must change password" flag set (Forms Au
- Index(es):
Relevant Pages
|
