.net code obfuscation

Question

4.00/5 (1 vote)

See more:

Hello dear's.......................

Can anyone tell me about how to create a setup package for obfuscated code in C# Windows Application?

Thanks in advance,

Gaurav kumar
Software Developer
;)

Posted 12-Jan-11 1:47am

gaurav.ipec

Updated 12-Jan-11 1:52am

Estys

v2

Add a Solution

4 solutions

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)

jmcc2k · Answer 1 · 2011-01-12T19:12:00

Solution 4

You will typically need to obfuscate the assemblies AFTER they are built but BEFORE they are put in the setup package. This can be done using MSBUild integration of the obfuscation step in your build process. See Crypto Obfuscator which supports this scenario.

Posted 12-Jan-11 19:12pm

jmcc2k

#realJSOP · Answer 2 · 2011-01-12T01:52:00

Solution 1

What obfuscation package? Have you asked the manufacturer of the obfuscation package for help?

Posted 12-Jan-11 1:52am

#realJSOP

Mahmudul Haque Azad · Answer 3 · 2011-01-12T05:11:00

Solution 3

Well you can create Merge Module (msm file) for obfuscated code and later when you will create the installer (msi file) just merge the msm here...

Follow this MSDN[^] page to get the idea about MSM and MSI and how to create them. :)

Posted 12-Jan-11 5:11am

Mahmudul Haque Azad

amp_dude · Answer 4 · 2011-08-31T10:41:00

I agree with jmcc2k above. However, if you don't have a sophistocated Obfuscator and/or yo don't want to mess with editing the MSBuild, then you can try my solution below.

If you are using the included Dotfuscator CE in Visual Studio, a relatively easy (but cumbersome) way to do it is:
1) Build your executable the normal way.
2) Run Dotfuscator.
3) Using Windows Explorer, manually overwrite the exe you generated from step 1 above with the one generated by the Dotfuscator (i.e., copy the Dotfuscated exe and paste it where the original exe file is, which is probably in your Release folder).
4) Create a setup project and build that. The setup project will see the exe file and won't care that it came from Dotfuscator.