Software Deployment

In the property table ROOTDRIVE=C:\

I tried that..It again takes the application to C:\ drive alone.I
s it not possible to decide the drive at the time of installing the msi?

Ren,
Are you worried about drive space issues? Otherwise you can't install an app to both drives unless they are just data files which don't affect sys state.

In essence; my question is - why?
Regards
Wayne

WayneB,
My question is,If INSTALLDIR=D:\ does not work in command prompt, Is there ay other option to do that.Because my requirement is that,the same package has to install in D:\ when desired and in C:\ when needed.

create 2 different transforms
In transform 1, the property table ROOTDRIVE=C:\
In transform 2, the property table ROOTDRIVE=D:\

you will not be able to install the same product on BOTH C: and D: drives CONCURRENTLY on the same system, if that's what you're asking

Hi,
The package gets installed in D drive with the help of custom action.This takes the entire package to D.Is there any option by which we can install the system related files in C and the rest in D.Because installing the entire application in D does not allow certain shortcuts to launch.Can anyone help me on this please.Thanks in advance

Is there any option by which we can install the system related files in C and the rest in D.
No. Your only option for that would be to split the package into two separate ones. If it's a vendor-supplied MSI, then that's pretty much a non-starter.

Because installing the entire application in D does not allow certain shortcuts to launch.Why? What happens? If the app errors because it's unable to find its files, just add INSTALLDIR to the PATH environment variable.

Hi,
Adding property ROOTDRIVE willnot be hardcoding the path? is this right practise to do...Is there no other way to do this.


Please suggest

Yes there's another way, let Windows Installer handle it.
http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx

If ROOTDRIVE is not set at a command line or authored into the Property table, the installer sets this property. During an administrative installation the installer sets ROOTDRIVE to the first connected network drive it finds that can be written to. If it is not an administrative installation, or if the installer can find no network drives, the installer sets ROOTDRIVE to the local drive that can be written to having the most free space.

In essence; my question is - why?
Regards
Wayne
I agree with Wayne's question of why would one want to do this? I dont see any reason why one would want to this unless its to try something out. I feel installing the same application simulataneously in two drives would sabotage the working of the application as the registry references would be associated with one of the drives, in turn making the files and folders instead in the other drive to be simply useless. Please correct me if I am wrong and also if Ren or someone else might come up with a specific reason why one would one will have to do such a thing.

Cheers,