The .exe application file isn't obfuscated after installing setup ?
-
Hi, I am creating a setup project for my solution in C#, and I created a merge module that include all obfuscated assembly files (.dll files, and the .exe file), then add it to the setup project Before building the setup project, I replace assembly files (in the Bin/Debug) by obfuscated files. After building the project, .dll files still are obfuscated, however the .exe file isn't obfuscated. Are there anyone know how to fix that ? Thank you very much !
-
Hi, I am creating a setup project for my solution in C#, and I created a merge module that include all obfuscated assembly files (.dll files, and the .exe file), then add it to the setup project Before building the setup project, I replace assembly files (in the Bin/Debug) by obfuscated files. After building the project, .dll files still are obfuscated, however the .exe file isn't obfuscated. Are there anyone know how to fix that ? Thank you very much !
I suspect, from this question, that you are manually obfuscating the file. When your setup is built, though, it rebuilds the executable, so that the file is no longer obfuscated - (you'll see the same behaviour if you manually apply a certificate to your code). The trick is to run the obfuscation process as a PostBuild process - which means that the setup will get the obfuscated version.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
I suspect, from this question, that you are manually obfuscating the file. When your setup is built, though, it rebuilds the executable, so that the file is no longer obfuscated - (you'll see the same behaviour if you manually apply a certificate to your code). The trick is to run the obfuscation process as a PostBuild process - which means that the setup will get the obfuscated version.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easierThanks Pete very much, Could you please tell me more how to use PostBuild process ? I'm using the Crypto Obfuscator software to obfuscate assembly files. And I can see the properties of Setup project include the PostBuildEvent but I don't know how to use it (I am using Visual Studio 2010) Thanks and regards, Tai
-
Thanks Pete very much, Could you please tell me more how to use PostBuild process ? I'm using the Crypto Obfuscator software to obfuscate assembly files. And I can see the properties of Setup project include the PostBuildEvent but I don't know how to use it (I am using Visual Studio 2010) Thanks and regards, Tai
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easierHi Pete, thank you Could you tell me more detail about creating obfuscated setup project ? My solution includes some project: 1. Start up project (create application file) 2. Library projects (create dll files) 3. Merge project (include obfuscated assembly files) 4. Setup project Thanks and regards,
-
Hi, I am creating a setup project for my solution in C#, and I created a merge module that include all obfuscated assembly files (.dll files, and the .exe file), then add it to the setup project Before building the setup project, I replace assembly files (in the Bin/Debug) by obfuscated files. After building the project, .dll files still are obfuscated, however the .exe file isn't obfuscated. Are there anyone know how to fix that ? Thank you very much !
Hi, You can drag and drop the project file to Eazfuscator.Net and it will handle the Obfuscation of your binaries every time you compile with release, if you are using different Obfuscator check how to obfuscate the project file, I believe rebuilding your solution is recompiling the .exe and overwrite your Obfuscated .exe then the setup project will include the new non-Obfuscated file.
-
Hi, You can drag and drop the project file to Eazfuscator.Net and it will handle the Obfuscation of your binaries every time you compile with release, if you are using different Obfuscator check how to obfuscate the project file, I believe rebuilding your solution is recompiling the .exe and overwrite your Obfuscated .exe then the setup project will include the new non-Obfuscated file.