
zhenLi20184004074003 asked a question.
Setup type
Hi,
I have two setup type: one is client, theone is server.
I need copy two different sets of files for the client and server.
Could you give me some quick guidance?
Best,

zhenLi20184004074003 asked a question.
I have two setup type: one is client, theone is server.
I need copy two different sets of files for the client and server.
Could you give me some quick guidance?
Best,
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
You do not state what type of installer you are using.
I have an installer that contains files for a server install, and files for client install. It also has files that are common to all.
I am using a basic MSI install.
In my project I have one main Feature for all common files. Under this feature I have a feature for Server and a feature for Client. I set conditions on the feature InstallLevel so that only one or the other can be installed. As added insurance, for my server specific files, I add a component condition, and likewise for client specific components.
In my UI for the installer, I have a "feature dialog" that only allows the user to select one or the other feature. I happen to use radio buttons, but you could use simple button controls in place of your navigation buttons. For instance, instead of the user clicking 'Next' to continue, they would click "Server" or "Client". How you accomplish this is up to you, but behind the scenes you are setting appropriate property values that get evaluated for the features.
Finally, I have a number of custom actions that only run on a server install, and so for these I utilize the same property check as I do for my feature Install Level settings.