在我看来，混淆是一个想法，落入被隐藏的安全或虚假的安全感保护营地的地方。为了保护知识产权，有版权的;以prevent安全被发现的问题，还有的解决了那些问题的。总之，我认为这是一个技术解决一个社会问题。 那些几乎从来没有工作。

It seems to me obfuscation is an idea that falls somewhere in the "security by obscurity" or "false sense of protection" camp. To protect intellectual property, there's copyright; to prevent security issues from being found, there's fixing those issues. In short, I regard it as a technical solution to a social problem. Those almost never work.

不过，我似乎是唯一一个在我们的开发团队有这样的感觉，所以我现在不是错了，还是只需要令人信服的论据。我们的产品采用.NET，以及一个开发建议.NET反应堆（顺便说一下，建议在这SO线程以及）。

However, I seem to be the only one in our dev team to feel that way, so I'm either wrong, or just need convincing arguments. Our product uses .NET, and one dev suggested .NET Reactor (which, incidentally, was suggested in this SO thread as well).

.NET电抗器通过混合任何纯.NET程序集完全停止任何反编译（用C＃，VB.NET，Delphi.NET，J＃，MSIL ...）与本机code。

.NET Reactor completely stops any decompiling by mixing any pure .NET assembly (written in C#, VB.NET, Delphi.NET, J#, MSIL...) with native machine code.

所以，基本上，你把字节code所有优点远在一个去了？

So, basically, you throw all advantages of bytecode away in one go?

是否有良好的工程的利益混淆？

Are there good engineering benefits to obfuscation?

推荐答案

我张贴一个问题，可能会帮助你，因为它讨论了一些问题： should-i-be-worried-about-obfuscating-my-net-$c$c

I posted a question which might help you as it discusses some of the issues: should-i-be-worried-about-obfuscating-my-net-code