- changed milestone to 2.1.7a
- edited description
Integrate Repackaging and ConfuserEx steps as post build events for the Release step
When the released build is triggered from Visual Studio, the Post Build Events should handle the ILMerge and ConfuserEX steps. The resulting executable should be a merged and obfuscated executable
Comments (9)
-
reporter -
reporter Also exes obfuscated using ConfuserEX are being detected as virus by many antivirus softwares. Find the balance between this false positive and the need to obfuscate Getbhavcopy exe.
-
Hey Hemen, what about an idea of giving bse names and mcx eod.
Regards,
Deepak
-
reporter @DJ123143 , please restrict comments to the issue being discussed in this topic. If you do not see a relevant thread then please start a new issue, but do not cross post.
-
reporter - changed status to resolved
done with 2.1.7 release
-
reporter Version 2.1.7a release. Fixes
#15, fixes#16. BSE Indices fixes and automated release to obfuscate final exe→ <<cset e978a2850375>>
-
reporter - changed status to closed
-
reporter - changed status to resolved
Version 2.1.7a release. Fixes
#15, fixes#16. BSE Indices fixes and automated release to obfuscate final exe→ <<cset e978a2850375>>
-
reporter Issue
#6was marked as a duplicate of this issue. - Log in to comment