blocks|key|3372377|text|here解释了几乎所有关于.Net许可的内容。我认为不需要重写。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3372378|如果可以，最好从源代码管理中的项目中排除许可证文件。否则，编辑可视化组件可能是一件痛苦的事情。此外，在源代码控制存储库中存储许可文件也不是必需的。|3372379|希望这能有所帮助。|3372380|entityMap|0|LINK|mutability|MUTABLE|url|http://www.developer.com/net/csharp/article.php/3074001^0|0|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Almost everything about .Net licensing is explained <a href="http://www.developer.com/net/csharp/article.php/3074001" rel="noreferrer">here</a>. No need to rewrite, I think.

It is better to exclude license files from project in source control, if you can. Otherwise, editing visual components may be pain in the ass. Also, storing license files in source control repository is not a need.

Hope this helps.

blocks|key|3159699|text|这是不正确的。licx文件非常重要，对于构建嵌入了正确许可证信息的主机应用程序来说，它是必要的。因此，重要的是licx文件也要包含在源代码控制中。否则，签出另一台机器上的源代码的人将无法获得licx文件，构建可能会失败，或者在exe中没有所用组件的正确许可证信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3159700|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

That's not correct. The licx file is very important and is necessary for the host app to be built with the correct license info embedded in it. So, its critical that the licx files be also included in source control. Otherwise a person checking out the source code on another machine will not get the licx file and the build may fail or not have the proper license info for the used components in the exe.

blocks|key|3159810|text|这是一篇关于这个主题的很好的文章：Click+Here|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3159811|为了使用TX文本控件之类的授权组件部署应用程序，EXE文件必须正确授权。|3159812|.NET许可机制建议将许可证添加到EXE+-调用程序集。|3159813|-详细情况是什么？|style|BOLD|3159814|如果将TextControl从Visual+Studio工具箱拖放到窗体中，Visual+Studio将创建一个licenses.licx文件并包括许可证信息。此文件与项目文件位于同一文件夹中。|3159815|重要提示:+licenses.licx文件不包含许可证字符串本身。它只包含有关许可组件的信息。如果是TX文本控件(TXTextControl.TextControl)，则添加以下字符串：|3159816|TXTextControl.TextControl,+TXTextControl,+Version=15.0.700.500,+Culture=neutral,+PublicKeyToken=6b83fe9a75cfb638|code-block|syntax|javascript|3159817|如您所见，它包含命名空间和控件名称、程序集版本、区域性信息和唯一的公钥标记。基于该信息，许可证编译器(lc.exe)编译将嵌入到可执行程序集中的实际许可证字符串。lc.exe是Visual+Studio在构建过程中使用的.NET框架SDK的一个小实用程序。|3159818|-如果我在用户控件中使用TX文本控件怎么办？|3159819|在这种情况下，您还需要将许可证添加到主可执行文件中。因此，您可以简单地将TextControl拖放到主项目的虚拟形式中，以便自动添加licenses.licx文件和引用。|3159820|在此之后，您可以再次从该表单中删除TextControl。或者，您可以简单地将licenses.licx文件复制或创建到主项目文件夹。在这种情况下，您还需要手动添加对TX文本控件的引用。|3159821|entityMap|0|LINK|mutability|MUTABLE|url|http://www.textcontrol.com/en_US/blog/archive/20091015/^0|H|A|0|0|0|0|0|9|0|0|0|17|0|0|0|0|M|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1F|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1G|8|@$A|1H|B|1I|J|K]]|9|@]|C|$]]|$1|L|3|M|5|6|7|1J|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|1K|8|@$A|1L|B|1M|J|K]]|9|@]|C|$]]|$1|P|3|Q|5|R|7|1N|8|@]|9|@]|C|$S|T]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1P|8|@$A|1Q|B|1R|J|K]]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|1S|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1T|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]]]

This was a good article on the topic: <a href="http://www.textcontrol.com/en_US/blog/archive/20091015/">Click Here</a>

In order to deploy an application with licensed components like TX Text Control, the EXE file must be licensed properly.

The .NET licensing mechanism recommends to add the licenses to the EXE - the calling assembly. 

---- What happens in detail?

If you drag and drop a TextControl from the Visual Studio toolbox to a form, Visual Studio creates a licenses.licx file and includes the license information. This file is located in the same folder like your project file.

Important: The licenses.licx file does not include the license string itself. It just contains information about the licensed components. In case of TX Text Control (TXTextControl.TextControl), the following string is addded:

<pre><code>TXTextControl.TextControl, TXTextControl, Version=15.0.700.500, Culture=neutral, PublicKeyToken=6b83fe9a75cfb638
</code></pre>

As you can see, it contains the namespace and control name, the assembly version, culture information and the unique public key token. Based on that information, the License Compiler (lc.exe) compiles the real license string that will be embedded into the executable assembly. The lc.exe is a small utility of the .NET Framework SDK which is used by Visual Studio during the build process.

---- What if I am using TX Text Control in a user control?

In this case, you need to add the license to the main executable as well. Therefore, you can simply drag and drop a TextControl to a dummy form of the main project, so that the licenses.licx file and the references are added automatically.

After that, you can remove the TextControl from that form again. Or you can simply copy or create a licenses.licx file to the main project folder. In this case, you need to add a reference to TX Text Control manually as well.

I've encountered multiple third party .Net component-vendors that use a licensing scheme. On an evaluation copy, the components show up with a nag-screen or watermark or some such indicator. On a licensed machine, a Licenses.licx is created - with what appears to be just the assembly full name/identifiers. This file has to be included when the client assembly is built.

<ul>
<li>How does this model work? Both from component-vendors' and users' perspective.</li>
<li>What is the .licx file used for? Should it be checked in? We've had a number of issues with the wrong/right .licx file being checked in and what not</li>
</ul>

How does the Licenses.licx based .Net component licensing model work?

Visual Studio

编译器

我遇到过许多使用许可方案的第三方.Net组件供应商。在评估副本上，组件显示为nag屏幕或水印或某种类似的指示器。在获得许可的计算机上，将创建一个Licenses.licx，其中似乎只包含程序集的全名/标识符。在生成客户端程序集时，必须包括此文件。此模型是如何工作的？来自组件供应商和用户的perspective.What...

问基于Licenses.licx的.Net组件许可模型是如何工作的？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问基于Licenses.licx的.Net组件许可模型是如何工作的？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问基于Licenses.licx的.Net组件许可模型是如何工作的？
EN