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

Question

I've encountered multiple third part .Net component-vendors 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

Answer 1

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.

Answer 2

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.