It's absolutely unacceptable to have your controls rely on an external web service to check the license. The only thing you're going to get out of that is pissed off customers and maintenance issues for yourself.
I strongly encourage you to go with the honor system, or a very simple licensing key file (that never expires). You're selling a web site, not video games. Unless you know for a fact that you are losing significant money because of piracy of your product, do not waste your time. Remember the first rule of optimization!
you could build some sort of license controlmechanism into your website. therefore you could use the URL of the site (typically you sell your asp.net app for one or two urls to somebody), and e.g. you could also build some hardware-key-references into your license mechanism, so that a copy of your software is not possible to run on a different machine.
but keep in mind, all restrictions you build in will result in more work for your paying clients, and there is always somebody who want to try to use your software without paying it!
发布评论
评论（2）
让您的控件依赖外部 Web 服务来检查许可证是绝对不可接受的。 你唯一能从中得到的就是惹恼客户和给自己带来维护问题。
我强烈建议您使用荣誉系统或非常简单的许可密钥文件（永不过期）。 您销售的是网站，而不是视频游戏。 除非您确实知道您因产品盗版而损失了大量金钱，否则不要浪费时间。 记住优化的第一条规则！
It's absolutely unacceptable to have your controls rely on an external web service to check the license. The only thing you're going to get out of that is pissed off customers and maintenance issues for yourself.
I strongly encourage you to go with the honor system, or a very simple licensing key file (that never expires). You're selling a web site, not video games. Unless you know for a fact that you are losing significant money because of piracy of your product, do not waste your time. Remember the first rule of optimization!
您可以在您的网站中构建某种许可证控制机制。 因此，您可以使用该站点的 URL（通常您将您的 ASP.NET 应用程序出售给某人，以获得一两个 URL），例如，您还可以在您的许可证机制中构建一些硬件密钥引用，以便您的软件无法在不同的机器上运行。
但请记住，您建立的所有限制都会给您的付费客户带来更多的工作量，而且总有人想尝试在不付费的情况下使用您的软件！
you could build some sort of license controlmechanism into your website. therefore you could use the URL of the site (typically you sell your asp.net app for one or two urls to somebody), and e.g. you could also build some hardware-key-references into your license mechanism, so that a copy of your software is not possible to run on a different machine.
but keep in mind, all restrictions you build in will result in more work for your paying clients, and there is always somebody who want to try to use your software without paying it!