How to prevent decompiling the exe file?

Question

4.38/5 (4 votes)

See more:

Hi every one.
I made project in C# 2005 but I want to prevent decompiling the exe file.
I know there are many tools to decompile the exe file to sln or source file and I want to prevent it.
How can I do that?

Thanks.

Posted 26-Jan-10 23:23pm

dabbourabd

Updated 26-Jan-10 23:50pm

CPallini

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 18-Dec-10 21:00pm

Dotfuscator is known to be quite weak. Also, I once faces with the project that cause obfuscator to fail (not failed to obfuscate, failed to complete the task, obfuscator itself crashed during run-time; I don't remember the version, but in 2009). Finally, strictly speaking, the obfuscator does not prevent decompilation, it obfuscated, that is, make the result of decompilation hard to understand. Some commercial products primatily advertized actually offer stronger code protection features used to prevent debugging. (I don't know if preventing decompilation per se it possible, but your point is not decompilation, your goal is goal protection, is that true?)

4 solutions

Solution 5

You need to obfuscate your assemblies using something like Crypto Obfuscator - after obfuscating, you will not be able to make sense of your own code even if you can view it in Reflector.

Posted 9-Aug-12 0:24am

LogicNP

Comments

Amax2009 12-Apr-13 5:10am

I do not have any solution but i need to be helped to be protected my code because i do have many information in my application which is very important to me and Crypto Obfuscator is to encrypt my code which is not much helpful for me to protect those informations. So please give me any solution so that my exe could not be opened by .net reflector and any other applications which decompiles the exes.

Thanks!

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Accepted Answer · 2010-01-26T23:34:00

Like the other two guys said, you need an obfuscator utility, but don't use the one that comes with Visual Studio - it doesn't do nearly enough. You actually need to pay money for a decent one.

Also, you can't obfuscate WPF applications. I know this isn't an issue for you right now, but if you deploy a WPF app in the future, you won't be able to protect it from prying eyes.

Keith Barrow · Accepted Answer · 2010-01-26T23:30:00

You need a tool called an obstifucator (Honestly!).
Some versions of Visual Studio (the non-express ones I think) come with Dotfusticator, which is an obstifucation tool.

I don't know any details about how strong dotfuscicator is, as I have never really had to obstifucate in earnest. There are other paid and unpaid tools out there.

Abhinav S · Accepted Answer · 2010-01-26T23:29:00

Solution 1

dabbourabd wrote:
i want to prevent that

Using a tool like dotfuscator could be one way.

Posted 26-Jan-10 23:29pm

Abhinav S

v2

How to prevent decompiling the exe file?

4 solutions

Solution 5

Solution 3

Solution 2

Solution 1

Add your solution here

Preview 0