Need to access a file from Source Location
Hi,
I wanted to refer a file from Source Directory instead of INSTALLDIR. I tried using the property ADDSOURCE but it is not working.
In detail, I wanted a specific file not to be installed into INSTALLDIR but the shortcut should access it from Source location rather than accessing it from INSTALLDIR.
Is there any other ways that I can get this done?
Thanks in advance,
Susee.
I wanted to refer a file from Source Directory instead of INSTALLDIR. I tried using the property ADDSOURCE but it is not working.
In detail, I wanted a specific file not to be installed into INSTALLDIR but the shortcut should access it from Source location rather than accessing it from INSTALLDIR.
Is there any other ways that I can get this done?
Thanks in advance,
Susee.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
AngelD
15 years ago
how about setting the component to be "run from source" (msidbComponentAttributesSourceOnly attribute bit)?
Posted by:
anonymous_9363
15 years ago
Set the component to 'Run from Source' either in your authoring tool's UI or by altering the relevant component's Attribute to '1' (probably currently '0' - i.e. Run locally)
Posted by:
India_Repackaging
15 years ago
Hi Susee,
I think you can read the property SourceDir during installation and write its value to a registry key in a hive that belongs to your application. Then use a script to read this registry value to obtain the path from where your application was installed. The value of this registry will be the path your application was installed from. Make sure you read the property in Immediate as it will not be accessible in the Deferred mode.
I have never done what I have suggested to you, however I am going to definitely try it out myself.
I think you can read the property SourceDir during installation and write its value to a registry key in a hive that belongs to your application. Then use a script to read this registry value to obtain the path from where your application was installed. The value of this registry will be the path your application was installed from. Make sure you read the property in Immediate as it will not be accessible in the Deferred mode.
I have never done what I have suggested to you, however I am going to definitely try it out myself.
Posted by:
jmcfadyen
15 years ago
update to previous.
you can access SourceDir in the deferred phase however you need to implement CustomActionData.
additional to that SourceDir is not available early in the sequences. If you need it early you should sequence the ResolveSource standard action as well.
There is also another which may interest you which is OriginalDatabase property.
Take into consideration using the SourceDir is dependant on a deployment account that has network / source viewing rights. Deploying an application in Local System context using a deployment tool such as SMS with SourceDir CA's is likely to fail unless the machine accounts have perms to the network source.
you can access SourceDir in the deferred phase however you need to implement CustomActionData.
additional to that SourceDir is not available early in the sequences. If you need it early you should sequence the ResolveSource standard action as well.
There is also another which may interest you which is OriginalDatabase property.
Take into consideration using the SourceDir is dependant on a deployment account that has network / source viewing rights. Deploying an application in Local System context using a deployment tool such as SMS with SourceDir CA's is likely to fail unless the machine accounts have perms to the network source.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
