Eazfuscator.NET 仅在 SolutionConfiguration=Release 时工作
我使用 Eazfuscator 来“保护”我的 VS 项目 - 这意味着 Eazfuscator 在我的项目中添加了一个构建后事件，如下所示：
if /I "$(ConfigurationName)" == "Release" Eazfuscator.NET.exe [...]
我不确定为什么它会像这样检查 ConfigurationName - 我试图混淆构建，其中ConfigurationName = ForPlayers 所以这个检查会妨碍。
两个问题：
- 为什么Eazfuscator要做这个检查？
- 我可以让它不不做吗？我可以手动进入项目属性并将其删除，但这不是一个好主意，因为我是通过这样的脚本完成这一切的
：
Eazfuscator.NET.exe --protect-project [...] # add post-build event
devenv /build [...] # build the solution
Eazfuscator.NET.exe --unprotect-project [...] # remove post-build event
I used Eazfuscator to "protect" my VS project - this means Eazfuscator added a post-build event to my project that looks like this:
if /I "$(ConfigurationName)" == "Release" Eazfuscator.NET.exe [...]
I'm not sure why it's checking the ConfigurationName like that - I'm trying to obfuscate a build where ConfigurationName = ForPlayers so this check is getting in the way.
Two questions:
- Why does Eazfuscator do this check?
- Can I make it not not do it? I could manually go into the project properties and remove it, but that's not a good idea because I'm doing this all from a script like this:
.
Eazfuscator.NET.exe --protect-project [...] # add post-build event
devenv /build [...] # build the solution
Eazfuscator.NET.exe --unprotect-project [...] # remove post-build event
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
可能会进行此检查，以便 Eazfuscator 不会混淆用于调试的程序集，您可能需要 pdb 文件来逐步执行代码等。
在 Eazfuscator.NET v3 中进行了改进，以便您可以启用调试混淆的程序集。
您可以像这样简单地更新构建后事件：
This check is probably done so that Eazfuscator does not obfuscate assemblies used for debugging where you may need the pdb files to step through your code, etc.
With Eazfuscator.NET v3 there are improvements made so that you can enable debugging obfuscated assemblies.
You can simply update the post-build event like this:
Eazfuscator.NET 会检查发布配置，因为这是最常见的使用场景。大多数开发人员在想要发布时都会在“Release”中进行构建。
当然，您可以随意使用任何您喜欢的配置名称，只需按照 Rami A 的建议更新构建后事件即可。
Eazfuscator.NET does the check for Release configuration because this is the most common usage scenario. Most developers do builds in Release when they want to do a release.
Of course you are free to use any configuration name whichever you prefer, just update the post-build event as suggested by Rami A.