当涉及到。net时，如果你正在发布Windows窗体应用程序(或任何客户端有可移植可执行文件的应用程序)，它就有可能被破解。

如果你想坚持使用。net，并且想把你的源代码被窃取的几率降到最低，那么你可以考虑将它部署为ASP。NET应用程序，而不是使它成为一个Windows窗体应用程序。

net反应堆

更新

Jared指出de4dot声称能够反编译它。

.NET Reactor provides complete protection for your sensitive intellectual property by converting your .NET assemblies into unmanaged processes which cannot be understood as CIL, and which no existing tool can decompile. Hackers have no access to any intelligible form of your source. Powerful and flexible, the .NET Reactor licensing features allow you to enforce your license conditions and protect your revenue stream by using hardware and software locks. The license manager can build trial or permanent licenses, in a matter of seconds. A fully documented software development kit (SDK), complete with examples, allows you to call the licensing system directly from your code, allowing you to create custom extensions to the licensing system.

广义上讲，有三种人。

Those who will not buy your software and resort to cracks, or if they don't find any, not use your software at all. Don't expect to make any money from this group. They rely either on their own skills or on crackers (who tend to prioritize their time depending on your useful and how big your audience is. The more useful, the sooner a crack will be available). The group of legitimate users who will buy (pay for) your software, irrespective of what protection mechanism you use. Don't make life hard for your legitimate users by using an elaborate protection mechanism since they are going to pay for it in any case. A complex protection mechanism can easily spoil the user experience and you don't want this happening to this group. Personally, I'd vote against any hardware solution, which adds to the cost of your software. A minority who will resort to "unethical" cracking and will only pay for your software because its features are protected by a licensing mechanism. You probably don't want to make it exceedingly easy for this group to circumvent your protection. However, all that effort you spend on protecting your software will pay back, depending on how big this group of people is. This entirely depends on the type of software you're building.

根据您所说的，如果您认为有足够多的少数人可以被推动购买您的软件，那么请继续执行某种形式的保护。考虑一下你能从这些少数人身上赚到多少钱，与你花在保护上的时间相比，或者你花在第三方保护API/工具上的钱。

如果您想实现自己的解决方案，那么使用公钥加密是防止容易被黑客攻击的好方法(与对称算法相反)。例如，您可以对您的许可证(序列号或许可证文件)进行数字签名。解决这个问题的唯一方法就是反编译、修改和重新编译代码(你可以使用Simucal回答中建议的技术来增加难度)。

这真的值得吗?只要有足够的决心，任何保护机制都可以被打破。考虑你的市场、产品价格、客户数量等。

如果您想要更可靠的东西，那么就使用硬件键，但这相当麻烦(对用户来说)，而且成本更高。软件解决方案可能会浪费时间和资源，它们唯一会给你的是一种虚假的“安全感”。

还有一些想法(没有一个是完美的，因为没有完美的人)。

AntiDuplicate 改变语言，使用Skype的作者使用的好技巧 许可证服务器

不要在这上面浪费太多时间，因为破解者在典型技术方面有很多经验，比你领先几步。除非你想使用大量的资源，可能会改变编程语言(做Skype的方式)。

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

只是补充一个警告:如果你打算使用混淆，检查一切仍然工作!混淆可能会改变类名和方法名。因此，如果你使用反射来调用某些方法和/或类(就像在插件架构中)，你的应用程序在混淆后可能会失败。另外，堆栈跟踪对于跟踪错误可能是无用的。