I have a few questions about version 10 licensing and automated build systems. We have a build machine that creates new release builds and installs of our application. OUr application is branded into 4 or 5 different “applications”. Each of these applications are the same code, we just change the exe name, the config, and where it gets installed. The code is actually the same codebase. Our installer build process is what does the renaming and such. This was working fine in version 8 of ThinkGeo because we have our license key embedded in the application.
With the change to a generated license file, how will that work in our environment. There is no user interaction during our build process. I can’t create a license file before hand because the executable hasn’t been built yet. I am assuming the “generate license file” process in product center stores information about the executable within the license information since you have to browse to the exe to generate it. Is this true? I really hope not because in today’s world of CI/CD if the license file changes on each build of the application and new file has to get generated, then we are dead in the water.
My questions are
- Does the license process store information about the executable within the license information?
- If I can’t use the same license file that is generated BEFORE we do a build, then how do I automate the building of the license file so it can be included in the installers?