Dotfuscate Delayed Sign Troubleshooting

[Guest]

I'm trouble shooting my obfuscated program. I'd like suggestions on some
tools to help. I'm using vs2005 with delayed signing option from the
project settings and reading the hash from a key.snk file.

I sn -Vr to register it to ignore strong name verification and everything is
fine. I obfuscate and then sn -Vu to unregister it before finally sn -R to
resign the assembly.

I have runtime problems that can't find the obfuscated application/assembly.
I used the fusion log, and this is my latest progress.

Any help is appreciated.

 

[Frans Bouma [C# MVP]]

I'm trouble shooting my obfuscated program. I'd like suggestions on
some tools to help. I'm using vs2005 with delayed signing option
from the project settings and reading the hash from a key.snk file.

I sn -Vr to register it to ignore strong name verification and
everything is fine. I obfuscate and then sn -Vu to unregister it
before finally sn -R to resign the assembly.

I have runtime problems that can't find the obfuscated
application/assembly. I used the fusion log, and this is my latest
progress.

You should simply sign your app normally during compilation. then run
the obfuscator, and then run sn to re-sign the obfuscated version of
the assembly. That's what I do and works ok.

FB

--

 

[Guest]

Tried that. Thanks.


One tool that provides a little insight that I'm using is Fusion Log Viewer,
fuslogvw.

The log error is:
The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file
specified.Wait -- just had a thought. I was trying to isolate the problem
by just obfuscating one file, the exe to start. Not sure how this all
works, but should I obfuscate all referenced dlls as well? Does the
obfuscator coordinate references to external assemblies and rename them
consistently?Even system assemblies?
-jim

 

[SP]

Tried that. Thanks.


One tool that provides a little insight that I'm using is Fusion Log
Viewer, fuslogvw.

The log error is:
The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file
specified.Wait -- just had a thought. I was trying to isolate the problem
by just obfuscating one file, the exe to start. Not sure how this all
works, but should I obfuscate all referenced dlls as well? Does the
obfuscator coordinate references to external assemblies and rename them
consistently?Even system assemblies?
-jim

It will coordinate obfuscation within all the Input Assemblies you have in
your Dotfuscator project (which can be from one to all of the projects you
have in the solution). It won't touch external assemblies.

SP