/build/static/layout/Breadcrumb_cap_w.png

Clarification on [INSTALLDIR]

Hi All,

I require a clarification with [INSTALLDIR].

This is my situation:

I have my application whose [INSTALDIR] set to, say, 'Application1' under 'C:\Program Files\Softwares'. There are some other applications whose [INSTALLDIR] is set to, 'Application2' under 'C:\Program Files\Softwares'.

I need to allow the user to choose the [INSTALLDIR] during installation. So, if the user selects the location, the application would install under 'Appliation1' folder. But i need to have 'Softwares' as the starting path of install location. So, if i change the [INSTALLDIR] as 'Softwares' rather than 'Application1' such that my appl. gets installed under <Any Drive>\Program Files\Softwares(INSTALLDIR)\Application1.

Here is my question:

1. When i do that, will it conflict with other applications installing under 'Softwares' folder.
2. If there are some other applications installed under 'Softwares' say 'Application2', what happens
during uninstallation, will the installer removes the 'Softwares' folder completely
or only the 'Application' folder.
3. Please advise if there my approach is wrong.

Thanks.

0 Comments   [ + ] Show comments

Answers (7)

Posted by: anonymous_9363 16 years ago
Red Belt
1
ORIGINAL: vijayakumar
1. When i do that, will it conflict with other applications installing under 'Softwares' folder.
2. If there are some other applications installed under 'Softwares' say 'Application2', what happens
during uninstallation, will the installer removes the 'Softwares' folder completely
or only the 'Application' folder.
3. Please advise if there my approach is wrong.

1. Why would it? Each application is discrete and installs where the user directs it to (or to default if installed silently)
2. Why would it remove a folder it didn't create and which wasn't blank? MSIs only remove WHAT THEY INSTALLED. If a folder which an MSI created contains files which that MSI didn't install (in the case you describe, for example, or where an application creates data files not included in the MSI), it is ignored during uninstall
3. I can't imagine why you would want to add an additional level beneath 'Program Files' (since, after all, the purpose of that folder is to contain software...) but, if you want to, there's no reason not to.

It seems to me, however, that your question is connected to your post 'showArrow("4/16/2008 9:56:32 PM",34022,4,false) Unble to choose drive in 'Out of Disc Space' dialog!!! I'd be concentrating on that, rather than complicating how your workstations are set up.
Posted by: jmcfadyen 16 years ago
5th Degree Black Belt
0
you forgot to mention the plural of software is not softwares.
Posted by: vijayakumar 16 years ago
Orange Belt
0
Hi,

My msi has been created to install under [ProgramFilesFolder]<Vendor Name>\<Appl. Name>.

There are many products for the same vendor. so they will be installed under [ProgramFilesFolder]<Vendor Name>\<Appl2. Name>.

<Appl. Name> is the [INSTALLDIR] for my msi. Now the supplier have asked me to alter the msi to allow the install location to be selected by the user. So, when the user selects the location, say 'C:\Install', the appl. installs directly under C:\Install\<Appl.Name>.That is why i am asking whether changing the INSTALLDIR to point <Vendor Name>, will affect any other appl(<Appl2>, <Appl3>) installed under this folder in any case. If i uninstall my application, will it remove the <Vendor Name> folder, even if it has other appls. installed??

Hope i m clear in explaining my problem.

Thanks,
Posted by: jmcfadyen 16 years ago
5th Degree Black Belt
0
your explaining it as clear as mud.

I hope you were referring to [ProgramFilesFolder]<Vendor Name>\<Appl. Name> as an expression cos this is bad.

It should be written as [VendorName]<Appl. Name> in order to be correct or you will have issues with changing you [INSTALLDIR]
Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: vijayakumar
If i uninstall my application, will it remove the <Vendor Name> folder, even if it has other appls. installed??


2. Why would it remove a folder it didn't create and which wasn't blank? MSIs only remove WHAT THEY INSTALLED. If a folder which an MSI created contains files which that MSI didn't install (in the case you describe, for example, or where an application creates data files not included in the MSI), it is ignored during uninstall

I thought *my* explanation was pretty clear...

Besides, this question could be answered simply enough by basic experimentation. You *must* surely be packaging with VMs/VPCs (and if you're not, why not?) so how hard would it be to build a couple of packages to test out the theory and satisfy yourself that it works as I ghave explained?
Posted by: aogilmor 16 years ago
9th Degree Black Belt
0
ORIGINAL: vijayakumar
My msi has been created to install under [ProgramFilesFolder]<Vendor Name>\<Appl. Name>.
There are many products for the same vendor. so they will be installed under [ProgramFilesFolder]<Vendor Name>\<Appl2. Name>.
<Appl. Name> is the [INSTALLDIR] for my msi. Now the supplier have asked me to alter the msi to allow the install location to be selected by the user. So, when the user selects the location, say 'C:\Install', the appl. installs directly under C:\Install\<Appl.Name>.That is why i am asking whether changing the INSTALLDIR to point <Vendor Name>, will affect any other appl(<Appl2>, <Appl3>) installed under this folder in any case. If i uninstall my application, will it remove the <Vendor Name> folder, even if it has other appls. installed??

No. It would only remove the <vendor name>\appl.name directory. Some tools have a template that sets INSTALLDIR to [ProgramFilesFolder]\[Manufacturer]\[ProductName] [ProductVersion]

As Ian suggests, familiarize yourself with Windows Installer rules and properties.
Posted by: vijayakumar 16 years ago
Orange Belt
0
Yes. I created a small msi package and tested the condition practicall. It worked the same way, as you mentioned.

Thanks.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ