Create Obfuscated Setup in VS2010 Using .Net Reactor

Question

I am using .Net Reactor To Obfuscate my project. In my project I have about 10 dlls. I want my setup to deploy the obfuscated dlls in client's machine.

I tried putting the code below in Post-Build Event at Properties of the setup Porject.

"C:\Program Files\Eziriz\.NET Reactor\dotNET_Reactor.exe" -project "E:/s.nrproj"

But when i deploy it and try to open the deployed dlls in Reflector, it Opens and show the code. Where/What am i missing???

why you don't obfuscate the codes in your machine and put the files for deploying? — Mehdi Khademloo
– Mehdi Khademloo, Commented Sep 21, 2014 at 4:50
Obfuscate your dlls separately and then check them by Reflector to be sure your obfuscator works. — Ali Sepehri
– Ali Sepehri, Commented Sep 21, 2014 at 4:57
yes, if we obfuscate them separately on .Net Reactor's window then it works, but when we try to build setup using these separately obfuscated dlls, Dependency error occurs. — Bunzitop
– Bunzitop, Commented Sep 21, 2014 at 5:01
When you obfuscate your assemblies it is possible that .NET cannot recognize your dependencies automatically. But what kind of dependency error do you have? It cannot find an assembly? — Ali Sepehri
– Ali Sepehri, Commented Sep 21, 2014 at 5:06
Also if you want to use previous method, you should use Pre-Build instead of Post-Build. (You shouldn't obfuscate your setup project, do you know this?) — Ali Sepehri
– Ali Sepehri, Commented Sep 21, 2014 at 5:08

peter.cyc · Accepted Answer · 2014-10-15 11:21:35Z

1

Dot Net Reactor obfuscates exe's and dll's and stores them in a different location. Default is the sub folder Secured where the assemblies were. Be sure to take the secured ones and not the original ones in your deployment scheme !

answered Oct 15, 2014 at 11:21

peter.cyc

1,8121 gold badge13 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Ali Sepehri · Accepted Answer · 2014-09-21 05:18:03Z

0

You should obfuscate your assemblies before building your setup project, therefore you should use your command in Pre-Build instead of Post-Build. When you obfuscate your assemblies it is possible that .NET cannot recognize your required assemblies automatically. I strongly recommend that obfuscate your assemblies separately and then create your setup project (ensure that all of required assemblies are added to your project).

NOTE: There is some bugs about creating setup project in VS2010, sometimes closing and opening the visual studio works.

answered Sep 21, 2014 at 5:18

Ali Sepehri

2,5182 gold badges21 silver badges27 bronze badges

Comments

Vlad · Accepted Answer · 2016-11-09 18:22:41Z

0

This works on my side:

if /I "$(ConfigurationName)" == "Release" "C:\Program Files (x86)\Eziriz\.NET Reactor\dotNET_Reactor.Console.exe" -file "$(TargetPath)" -targetfile "$(TargetPath)" -q

and if you want to set config proj then add it like this:

-project "$(SolutionDir)obfuscation_settings.nrproj"

Given that .net reactor project is placed in solution folder and its name obfuscation_settings.nrproj

Good luck

edited Nov 9, 2016 at 18:22

answered Nov 9, 2016 at 18:11

Vlad

8881 gold badge10 silver badges31 bronze badges

Comments

Eziriz · Accepted Answer · 2020-11-12 15:56:37Z

0

The Post-build event doesn't work in this case. You can use the .NET Reactor VS Add-in in order to obfuscate the assemblies at the right time. The solution is described here: Solution

answered Nov 12, 2020 at 15:56

Eziriz

4114 silver badges5 bronze badges

Collectives™ on Stack Overflow

Create Obfuscated Setup in VS2010 Using .Net Reactor

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related