Using Launch Conditions
Hi ,
I am packaging SQL Client 2000 standard. The requirement is that the application needs to be installed to E:\ Drive. And i have created the package according to this.
I tested the application on a machine where there is an E:drive and everything went fine.
But when i tested the application on a machine where there is no E:\ Drive, it is throwing up an error saying "No E:\ Drive found".
I understood that i need to write a launch condition which checks whether the E:\ Drive is present or not. and then..........
I need to know how can tht launch condition be written in 2 cases.
Case 1: Check if E:drive is present. If present, install the application. If not present, pop up a dialog box mentioning "For this application to be installed, E drive must exist on the machine".
Case 2: Check if E drive is present.If present, install the application. If not present, it shouls atleast give me an option to install into C:drive.
Please help me out in this. Atleast i need an answer in one case.
Thanks in Advance,
elziarun
I am packaging SQL Client 2000 standard. The requirement is that the application needs to be installed to E:\ Drive. And i have created the package according to this.
I tested the application on a machine where there is an E:drive and everything went fine.
But when i tested the application on a machine where there is no E:\ Drive, it is throwing up an error saying "No E:\ Drive found".
I understood that i need to write a launch condition which checks whether the E:\ Drive is present or not. and then..........
I need to know how can tht launch condition be written in 2 cases.
Case 1: Check if E:drive is present. If present, install the application. If not present, pop up a dialog box mentioning "For this application to be installed, E drive must exist on the machine".
Case 2: Check if E drive is present.If present, install the application. If not present, it shouls atleast give me an option to install into C:drive.
Please help me out in this. Atleast i need an answer in one case.
Thanks in Advance,
elziarun
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
I can't see how you would cater for both cases you outline, other than writing some script.
Normally, you'd have just Case 1, in which case (sorry), you need to use System Search in conjunction with LC. Note, if using Wise, that it defaults to having the System Search action after LC.
So set a search for the registry key which causes the E: drive mapping (HKCU\Network\E) and populate a property with what it returns. The LC then tests for that property.
Normally, you'd have just Case 1, in which case (sorry), you need to use System Search in conjunction with LC. Note, if using Wise, that it defaults to having the System Search action after LC.
So set a search for the registry key which causes the E: drive mapping (HKCU\Network\E) and populate a property with what it returns. The LC then tests for that property.
Posted by:
elziarun
16 years ago
Hi,
Thanks for the valuable suggestion.
But i want to know how can i include system search along with the LC.
Can you please give me the syntax of the launch condition to be used?
Because, there is already a property named EDRIVE of value E:\ which i created.
Now when i am building a new launch condition, the condition builder gives me the option to choose from property, feature, component, Env variable.
I chose property and selected "EDRIVE" which is availble in the list. After this i am not able to proceed what i need to write in the launch condition.
Can you please help me out with this?
Thanks,
elziarun.
Thanks for the valuable suggestion.
But i want to know how can i include system search along with the LC.
Can you please give me the syntax of the launch condition to be used?
Because, there is already a property named EDRIVE of value E:\ which i created.
Now when i am building a new launch condition, the condition builder gives me the option to choose from property, feature, component, Env variable.
I chose property and selected "EDRIVE" which is availble in the list. After this i am not able to proceed what i need to write in the launch condition.
Can you please help me out with this?
Thanks,
elziarun.
Posted by:
anonymous_9363
16 years ago
I'm sorry, I don't have time to create a step-by-step guide for you. Download the SDK from MS and check MSI.CHM (if your authoring tool hasn't already installed it)
Posted by:
elziarun
16 years ago
Hi,
Thanks for the advice. But as time is pressing upon me, I thought of creating a transform file for the MSI where i can change the installation path and delivered it to the client.
It solved the problem [:)]. Neways thanks for the reply.
Cheers,
-elziarun.
Thanks for the advice. But as time is pressing upon me, I thought of creating a transform file for the MSI where i can change the installation path and delivered it to the client.
It solved the problem [:)]. Neways thanks for the reply.
Cheers,
-elziarun.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.