I asked your support and they said that this is not possible so I guess this is an Feature Request.
What I would like to do is to distribute my program in two files. The first is the exe file containing the program and installer. The second file is the license file. When I run the exe file it installs my program and copies the license file to the same directory as the program.
The reason for this is that I don´t wont to rebuild the installation package, with the right license file, everytime I´m sending a program to my customer.
If I make a package that is not build into one file I have to zip it when sending it per email. I want it to be as simple as possible for my customer. He usually is not either intrested in copying license files back and forth. 8)
Kenneth Lundström
Suggested Articles
Hello,
I have the same requirements. Our licencing is implemented both as a PIDKEY and some additional external files. I'm not necessary looking for an implemented solution but for some advice as to the best approach. I see these possibilities
1. ship a dummy licence file in the main installer package, which the customer then replaces at install time by making an admin image and then manually copying over the real licence files.
+ simple and concise for many who are not familiar with windows installer
- not sure how upgrades and the like are affected by this.
2. for each licence file, we build a patch, which we ship to the customer instead of the base licence files.
+ more "standard" way of applying updates
- more complex. Also I'm wary of patches. Would prefer transforms as this seem more stable, but can a transform be used to add files?
3. Use a separate installer for the licence files. We can build this for the customer. The licencing code in our app then uses the MSI apis to locate the file location licencing components in the separate installer.
+ allows independent update of the licencing files separate from the main program, e.g. with GPO Software Installation
- customer has to manage two installations
- end users might be confused by having two entries in Add/Remove programs for our product.
Are there other possibilities?
Thanks in advance for any insight you can provide!
Mat McGowan
I have the same requirements. Our licencing is implemented both as a PIDKEY and some additional external files. I'm not necessary looking for an implemented solution but for some advice as to the best approach. I see these possibilities
1. ship a dummy licence file in the main installer package, which the customer then replaces at install time by making an admin image and then manually copying over the real licence files.
+ simple and concise for many who are not familiar with windows installer
- not sure how upgrades and the like are affected by this.
2. for each licence file, we build a patch, which we ship to the customer instead of the base licence files.
+ more "standard" way of applying updates
- more complex. Also I'm wary of patches. Would prefer transforms as this seem more stable, but can a transform be used to add files?
3. Use a separate installer for the licence files. We can build this for the customer. The licencing code in our app then uses the MSI apis to locate the file location licencing components in the separate installer.
+ allows independent update of the licencing files separate from the main program, e.g. with GPO Software Installation
- customer has to manage two installations
- end users might be confused by having two entries in Add/Remove programs for our product.
Are there other possibilities?
Thanks in advance for any insight you can provide!
Mat McGowan
-
MadButcher
- Posts: 1
- Joined: Wed Apr 19, 2006 3:43 pm
- Location: The Netherlands
Hi there,
I would think there is also the possibility of using a custom action in the commit section. Here you can check the license file is there and if not the user might choose to run a trail version, order a license by email or retrieve the license file from a website (in our case a customer portal).
As far of the GPO part, I think it is a better practice to install the license on the server with a license service in any form. This way you can also check the number of client installations (Which in turn should also be checked by the installer if there is a restriction in the number of clients that might install the software)
I think i am going to use this in the future as well, but at this point i'm still evaluating AI
Greetings,
Butch
I would think there is also the possibility of using a custom action in the commit section. Here you can check the license file is there and if not the user might choose to run a trail version, order a license by email or retrieve the license file from a website (in our case a customer portal).
As far of the GPO part, I think it is a better practice to install the license on the server with a license service in any form. This way you can also check the number of client installations (Which in turn should also be checked by the installer if there is a restriction in the number of clients that might install the software)
I think i am going to use this in the future as well, but at this point i'm still evaluating AI
Greetings,
Butch