.NET类库发牌理念 - 疯狂？ [英] .NET class library licencing idea - madness?

问题描述

你好我目前正在开发一个.NET库（不是控制），并考虑如何提供一个组合的发展和自由运行时部署许可方案与它合作。

Hi I'm currently developing a .NET library (not a control), and considering how to provide a combined "development" and freely run-time deployable licencing scheme to work with it.

我想对开发商的许可，某种类型的节点锁定会就好了（文件和/或服务器/网络服务），但我想允许开发者免费分发我的软件在运行时。

I'm thinking for developer licencing, some kind of node-locked will be just fine (file and/or server/web service), but I want to allow developers to freely distribute my software at run-time.

我是游荡，如果在运行时许可证，这将是一个不错的主意，有作为说一个MD5散列牌照键，调用组件（或可执行文件/模块 - 不知道）的一部分，公司的信息，或也许是自己的强名称的哈希键？

I was wandering if for the run-time licence, it would be a good idea to have as part of say an MD5 hash for the licence key, the calling assembly's (or executable/module - not sure) company info, or perhaps it's own strong name hash key?

这将意味着我的用户将有自己的软件发布/分布每次生成一个运行时许可证，但应该不会太苛刻，我想。这可以从有效开发完成/建造许可/节点锁定机器，制作过程pretty的简单和轻松。

It would mean my users would have to generate a run-time licence every time their software was released/distributed, but that shouldn't be too onerous, I think. This could be done from a valid dev/build licenced/node-locked machine, making the process pretty simple and painless.

这是非常多的想法在这个阶段。我很乐意听到的任何想法的人可能有这样的想法。

This is very much an idea at this stage. I'd love to hear any thoughts people may have on this idea.

推荐答案

有关这几个想法：

• 我相信这是乔尔斯波斯基谁指出，你必须做出一个许可证的AQUISITION比破，对不起，工作围绕软件的授权机制更容易。具有节点锁定软件开发工作，这可能是在背面有疼痛感，特别是如果你有一机多用。也许看看基于用户的许可（即我的用户有一个许可证的地方在他们的个人资料，如果不是已在使用，你可以使用它，不管你是在哪台机器）。
• 在我预见到的问题具有无限的运行许可证，但仍要求为一样的库单机开发人员许可证您双重许可制度。例如，是什么阻止开发商许可证运行时为他们的发展目的是什么？
• 执行是另一个问题。你如何找出如果您的客户端违反许可协议？具有图书馆手机之家最有可能排除其使用了很多企业，有防火墙的环境。
• 多少努力，你会不得不投入到这个计划？你能买吗？你可以用时间来提高你的库中，以便您的客户会购买一个升级呢？
• 如果有任何可比库在那里，检查他们是否有任何形式的复制保护。如果不是，忘掉它直线距离，你会交给销售到你的竞争对手的方式。

• I believe it was Joel Spolsky who pointed out that you have to make the aquisition of a licence easier than breaking, sorry, "working around" the licensing mechanism of the software. Having worked with node locked software as a developer, this can be a pain in the backside, especially if you have more than one machine. Maybe look at user-based licensing (ie, my user has a single license somewhere on their profile, and if that isn't in use already you can use it no matter which machine you're on).
• I foresee problems with your dual licensing scheme of having unlimited runtime license, but still requiring a per-seat developer license for the same library. For example, what's stopping developers to 'license' a runtime for their development purposes?
• Enforcement is another problem. How do you find out if your client is violating your license agreement? Having the library "phone home" would most likely rule out its use in a lot of corporate, firewalled environments.
• How much effort would you have to invest into this scheme? Can you buy one? Can you use the time to improve your library so your clients would buy an upgrade instead?
• If there are any comparable libraries out there, check if they have any sort of copy protection. If not, forget about it straight away as you'll be handing sales to your competitors that way.

这篇关于.NET类库发牌理念 - 疯狂？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！