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

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.

• How does this model work? Both from component-vendors' and users' perspective.
• 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

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.

Almost everything about .Net licensing is explained here. 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.

This was a good article on the topic: Click Here

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:

TXTextControl.TextControl, TXTextControl, Version=15.0.700.500, Culture=neutral, PublicKeyToken=6b83fe9a75cfb638

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.