default Installation directory is pointing to C:\
Hello,Have couple of questions
default Installation directory is pointing to C:\app. It is an msi. By using INSTALLDIR if I change it to C:\Program Files (x86)\app, will it create any problem?
Second: The appver is 9. The upgrade is also to be applied. upgradever is 10. When I try to install upgrade directly, it is looking for the path C:\app. So, shall i browse and point it to C:\Program Files (x86). Does it effect the functionality of app?
Thank You guys. Please share your thoughts
-
Changing INSTALLDIR should not be a problem.As you said upgrade is looking for the path c:\app...when exactly does it look for this path...If you have option to browse and change that, you can definitely do it but check the installation and functionality thoroughly. - deepali 10 years ago
Answers (5)
C:\Apps are generally for 16 bit applications. So if it is a 16 bit application, then it will be a problem if you change your directory to C:\Program Files (x86)\apps
Otherwise there is no issue in changing the path. Check if it works fine.
~Piyush Nasa
~My Blog: http://msiworld.blogspot.com/
Thank You all so much. I will give a point to one and all.
Yesterday, I tried to change the default directory from c:\apps to c:\program files (x86)\app and even I changed the ini to point it to the same but no success. It is copying part of the directories/files to c:\apps still and rest to c:\program files (x86)\apps maiin install is copying to c:\app though. Even couple of other packagers tried but no success. So we decided to put in c:\app folder.
Thanks again.
Some apps (Oracle?) really don't like 'spaces' in their paths and will generate problems if you do so.
Ah confusing.
Right, it shouldnt be a problem if the vendor MSI logic is good. You can just chanage the INSTALLDIR property to change the install location. Do some testing and see what happens, its all about the testing - test test test.
I dont see it being a problem, but if you are really worried you can move the RemoveExistingProducts higher up in the execute sequence to effectively remove the product first, then install the new product.
And no it shouldnt effect the app, again it comes out in the testing.
I would counsel against using hard-coded paths like that. Rather, I'd use the Directory table, making the changes via a transform, obviously.