Developer License Guidelines
These guidelines answer the common questions about how the developer license works.
What's included? The CMarkup product components include all classes like
CMarkupMSXML, and in the Advanced product the
How many licenses do I need? You need a developer license for every developer that programs these CMarkup components into your projects.
Can I keep copies? You can have copies and archives of the CMarkup component source code as part of the build process and configuration management of your projects.
What about other developers? Other developers on the same team who do not actually program to the functions of the CMarkup components do not need licenses to compile the project containing them.
When the developer leaves? The agreement allows for transferring between developers when a developer leaves a project and will not take the CMarkup product elsewhere.
Distribution? CMarkup components are only available for compiling into binary products, not products in which any part of the CMarkup source code will be distributed.
Belongs to consultant or client? If you are developing for a client who owns the project source code, then the developer license should be purchased for that client to remain with the client and the project source code.
Absolutely. The point of the developer license is to give you unlimited royalty-free use in your binaries. Unlike seat licensing it is based on the number of developers that actively program with it, not the number of units you sell or distribute. Redistribution restrictions are only placed on the uncompiled source code text (whether modified or not) which must be kept within your company; i.e. your product cannot consist of pieces or derived pieces of the source code text in Markup.cpp or Markup.h. In addition, there is *no* requirement to tell your customers you used CMarkup, or anything like that. While your upgrades last for one year, any releases of CMarkup developer version you receive during that year are yours to use in your products indefinitely.