obfuscation need

[GaryDean]

I used the Community Edition of the obfuscator that comes with vs2005 and
using it produced the following error:

Could not load file or assembly 'GP2' 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)

The help file with this software is for their professional edition ($1,800)
and is no help for this "software" that comes with VS.

Can this Community Edition be made to work?
--
Regards,
Gary Blakely

[Walter Wang [MSFT]]

Hi Gary,

The HRESULT 0x80131045 means FUSION_E_SIGNATURE_CHECK_FAILED. It means
fusion failed to validate the strong name signature of your assembly.
Either your assembly is corrupted, or your assembly is delay signed:

#Junfeng Zhang's Windows Programming Notes : Assembly Delay Sign and
Assembly Installation
http://blogs.msdn.com/junfeng/archiv...11/549363.aspx

For further troubleshooting of Dotobfuscator issues, please refer to
following KB:

#License and support information for the Dotfuscator tool for Visual Studio
2005 or for Visual Studio .NET 2003
http://support.microsoft.com/kb/820664/

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[GaryDean]

The assembly isn't signed at all. The dll works fine and the obfuscated dll
gets this error.
Gary

--
Regards,
Gary Blakely
Dean Blakely & Associates
www.deanblakely.com
"Walter Wang [MSFT]" <wa****@online.microsoft.comwrote in message
news:FJ**************@TK2MSFTNGHUB02.phx.gbl...

Hi Gary,

The HRESULT 0x80131045 means FUSION_E_SIGNATURE_CHECK_FAILED. It means
fusion failed to validate the strong name signature of your assembly.
Either your assembly is corrupted, or your assembly is delay signed:

#Junfeng Zhang's Windows Programming Notes : Assembly Delay Sign and
Assembly Installation
http://blogs.msdn.com/junfeng/archiv...11/549363.aspx

For further troubleshooting of Dotobfuscator issues, please refer to
following KB:

#License and support information for the Dotfuscator tool for Visual
Studio
2005 or for Visual Studio .NET 2003
http://support.microsoft.com/kb/820664/

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Walter Wang [MSFT]]

Hi Gary,

Is assembly 'GP2' the file that being obfuscated? or is it an dependent
assembly that used by the one being obfuscated? Does this issue occur on
other system?

Again, I suggest you to contact Obfuscator's support site for better
resources on troubleshooting such issue.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.