Re: Dotfuscating Part of an Application

Nicole,

The error is as follows:

Encountered retargetable \'System.Drawing\' as at line 45, column 18.
Was expecting one of:
<HEXBYTE> ...
<SQSTRING> ...
<DSQSTRING> ...
<ID> ...
"retargetable" "retargetable" ...
"retargetable" <ID> ...
"retargetable" <HEXBYTE> ...
"retargetable" <SQSTRING> "." ...
"retargetable" <SQSTRING> "as" ...

Build Error.



If I'm getting this error with the Community Edition of the software, should
I expect anything different with a purchased version of it?

Can I ask you, do you think it's crazy to release commercial software that
is not obfuscated? I ask because this never seemed to be [as much of] a
problem with VB6 apps so I'm a little lost about what to do.

--
Robert W.
Vancouver, BC
www.mwtech.com



"Nicole Calinoiu" wrote:

"Robert W." <RobertW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9DDD4E86-8EE1-4B92-AA3C-6B0CE677DE7F@xxxxxxxxxxxxxxxx
I wanted to use Dotfuscator before releasing my commercial application. I
tried dotfuscating the entire EXE but it failed with some cryptic error
about
System.Drawing. I have no idea how to resolve that.

Would you be able to provide the full error details?


So then I thought the
next best thing would be to dotfuscate the DLLs that are part of the
application. I ran it on one and it seemed to work fine. But when I
copied
this DLL over top of the original one, the application would not run.

If you're using the Dotfuscator Community Edition that ships with VStudio,
you'll need to obfuscate all assemblies together as a group. This will
enable Dotfuscator to adjust the code in dependent assemblies to match the
obscated type and member names. You must do this even if you aren't
obfuscating anything in the dependent assemblies.


Is there something else one has to do to get an app to utilize a
dotfuscated
DLL?

--
Robert W.
Vancouver, BC
www.mwtech.com




.

Relevant Pages

  • Re: Dotfuscating Part of an Application
    ... tried dotfuscating the entire EXE but it failed with some cryptic error ... If you're using the Dotfuscator Community Edition that ships with VStudio, ... you'll need to obfuscate all assemblies together as a group. ... obfuscating anything in the dependent assemblies. ...
    (microsoft.public.dotnet.security)
  • Re: Keeps getting exception in dotfuscator output
    ... The exception I got was a file not found exception or something like ... So now I can obfuscate my app. ... When giving the release version as input to dotfuscator it says this ... use the "rename" feature. ...
    (microsoft.public.dotnet.framework)
  • Re: Protect IL Code
    ... "Alek Davis" wrote: ... then it can be configured to obfuscate only private and internal ... If DotFuscator ... >> We can configure obfuscator tool with a list of exception names that the ...
    (microsoft.public.dotnet.security)
  • RE: .NET and keeping my source code to myself...
    ... I understand that you need to obfuscate your assembly to ... Visual Studio .NET 2003 has provided us with a tool called Dotfuscator. ... Dotfuscator is an obfuscator for .NET assemblies. ... smaller and faster .NET applications. ...
    (microsoft.public.dotnet.general)
  • Re: obfuscation & reflection
    ... MrNobody wrote: ... > Now, I want to obfuscate as much of my program as I can, though if I ... For Dotfuscator, you can single out the classes you want excluded from ...
    (microsoft.public.dotnet.languages.csharp)