[C#] Protect against decompilers.

[Parker]

Hey there, I'm about to release my program to the public, what step(s) can I take to minimise (or completely stop) leeches from decompiling?

Sorry that I don't have that much time to actually take the time, but I've been searching for about 2 hours now and I have to get ready for my Dads.

 

[Aurora]

1) Dotfuscator, part of visual studio, scrambles code.
2) Dotnet Reactor encrypts exe file

You must be registered to see links

 

[Parker]

Okay thanks man, what about decompiling, do you know any that I can try out to see if it works on my program now?

 

[Aurora]

get Reflector .net dissasembler

 

[Parker]

Okay I'll look into it thanks.

 

[Intelext]

Ohh and compress your *.exe file.

 

[Daevius]

Be sure to include no debug information at all, and use all size compression technique's (strip binary symbols). Also, be sure to release in "Release" mode, rather then "Debug" mode.

And use UPX, google it

 

[DeathArt]

Since when did UPX work on .NET executeables? I was in the understanding it only worked on normal PE executeables in native code.

Just give up allready, you can't make a .NET application that cannot be decompiled.
Who cares if a few nerds can see the source.

 

[Daevius]

Since when did UPX work on .NET executeables? I was in the understanding it only worked on normal PE executeables in native code.

Oh sorry, yes that could be true.

Just give up allready, you can't make a .NET application that cannot be decompiled.
Who cares if a few nerds can see the source.

Every executable can be decompiled...it's extremely hard to make a good protection...I just protected it just a little bit, so it keeps off the newbies and doesn't challange the real crackers.

 

[Aurora]

dotnet reactor is the safest at the moment, there is no tools availible to directly unpack a exe/dll created with it.