Keeps getting exception in dotfuscator output

  • Thread starter Thread starter Marcus
  • Start date Start date
M

Marcus

I get exception when I try to run my c# windowsapplication after its
exe-file has been built with dotfuscator community edition. I can only
use the "rename" feature. But from what I have understood thats the
only thing available for this version.
My problem is that even if I exclude everything from beeing renamed and
then builds my assembly in dotfuscator, the output is useless,
prompting an exception. The input exe file is working fine.
How can this be?
 
Reverse engineer the IL with Reflector. You will probably find one of the
public elements that has been renamed, or similar.

If that does not work, post the exception message, so we are not shooting
around in the dark. :-)

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think outside of the box!
*************************************************
 
The exception I got was a file not found exception or something like
that. This was my fault, I did not put the obfuscated output in a
directory where the relative paths of files to be read by the app could
be found.

So now I can obfuscate my app. My problem now is I can only do it on
the debug version.
When giving the release version as input to dotfuscator it says this
during build:

writing assemblys...
External type not found c,Interop.IsLicenseDotNet, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null
Build error

The Interop.IsLicenseDotNet is a dll that I reference in my VS2003
project. I call methods which resides in that dll from my app.
What should I do with such dlls. I have only got the community edition
of dotfuscator so almost everything is disabled. Is it possible to
obfuscate a project with added references in community edition? I get
no complaints from dotfuscator about the System.XML, System.Data, ...
references that VS2003 adds by default when I create a windows
application?

Like things are now, I get to chose between the following 2
alternatives:
1) Release my application with debug information available and renamed
classes, methods, variables
OR
2) Release my application with no debug information available and with
all classnames, methodnames and variable names easily understood by a
human.

If there is no way I can get an assembly without debug information AND
with obfuscated naming, which one is the safest to release of 1) and
2)?



Cowboy (Gregory A. Beamer) skrev:
 
Back
Top