Use online update to block those unlicensed copies. Verify serial number from different modules of your application and do not use a single function call to do the verification (so that crackers cannot bypass the verification easily). Not only check serial number at startup, do the verification while saving data, do it every Friday evening, do it when user is idle ... Verify application file check sum, store your security check sum in different places. Don't go too far on these kind of tricks, make sure your application never crash/get into malfunction while verifying registration code. Build a useful app for users is much more important than make a unbreakable binary for crackers.

最好的答案是第一个来自小开发人员自己的经验，上面讨论的所有反反转技术对于任何严肃的反向工程师来说都是101个教科书案例。

一些商业DRM解决方案相当不错，但它们总是在数小时(或数天)内使用自定义DRM解决方案破解每一款AAA级游戏。只有一个全新的DRM解决方案的引入——有时——延迟是不可避免的，可能需要几个星期。

充分利用DRM需要花费大量的时间和金钱，而且很容易损害性能、可靠性、兼容性/可移植性和客户关系。要么坚持一些像样的商业DRM，不要试图太聪明，承担你的(更少的)损失，要么完全忘记它……

一个DRM解决方案的例子，它挖了自己的(商业)坟墓:http://en.wikipedia.org/wiki/StarForce

Here's one idea: you could have a server hosted by your company that all instances of your software need to connect to. Simply having them connect and verify a registration key is not sufficient -- they'll just remove the check. In addition to the key check, you need to also have the server perform some vital task that the client can't perform itself, so it's impossible to remove. This of course would probably mean a lot of heavy processing on the part of your server, but it would make your software difficult to steal, and assuming you have a good key scheme (check ownership, etc), the keys will also be difficult to steal. This is probably more invasive than you want, since it will require your users to be connected to the internet to use your software.

如果它是用。net编写并编译为CIL，则可以反映出来。如果安全性是一个问题，并且要避免混淆，那么我建议使用非托管语言编写应用程序，这种语言本质上更难以进行逆向工程。

下面是一些。net混淆工具的详细对比表:

截图来自obfuscators.io

你和很多人分享的秘密就不是秘密了。如果你的代码中有秘密的东西，混淆它是没有保护的;它只需要去混淆一次。如果你有什么秘密不想和你的客户分享，那就不要和你的客户分享。将代码编写为web服务，并将超级机密代码保存在自己的服务器上，只有您可以看到它。