protect my code from decompile

[Daylor]

how can i protect my code from decompile ?

 

[Thomas Scheidegger [MVP]]

With third party obfuscators:
http://www.gotdotnet.com/team/csharp/tools/default.aspx#obfuscators
or found with Google :
http://www.desaware.com/Ebook4L2.htm
http://www.desaware.com/downloadsqndl2.htm


Another solution is to write the (short) 'secret' code
in classic C++ and then use Managed C++ wrappers.

 

[Huihong Luo]

We offer a complete solution to protect your .NET source code from prying
eyes,

(1) salamander .NET decompiler, show how easy to get source code from the
..NET assemblies,
http://www.remotesoft.com/salamander/index.html

(2) obfuscator, make reverse engineering more difficult, the easiest to use,
support C#, VB.NET, J#, MC++, etc.
http://www.remotesoft.com/salamander/obfuscator.html

(3) protector, completely prevent disassembly (no more ildasm) and
decompilation, also offer string and resource protection,
http://www.remotesoft.com/salamander/protector.html

(4) native compiler, link and compile .NET executables to x86 native code,
run w/o .NET framework, coming soon,

Huihong
Remotesoft, Inc.

 

[Michael Giagnocavo [MVP]]

Another solution is to write the (short) 'secret' code

in classic C++ and then use Managed C++ wrappers.

The problem then becomes the link between the managed and unmanaged
code. Doing this just makes it easier for an attacker to isolate the
critical code, then bypass it completely.

-mike
MVP

 

[Michael Giagnocavo [MVP]]

Hello,

Using a commercial obfuscator, encrypted loader is a good start
(see response to "Licence Key generator", a few posts up). However
depending on the apps and the attack you are trying to prevent, you
might want to consider doing a lot of "custom" anti-reverse
engineering or anti-cracking code.

-mike
MVP

 

[Uri Dor]

I think the idea was that the 'secret' code also does the work
(proprietary algorithm, whatever), so bypassing it definitely doesn't
help in understanding its secrets.