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
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.