Page 1 of 1

MSI Package Location & Build

Posted: Thu Dec 08, 2016 6:04 am
by robert.eickleberry
Product, version and build:
(*** Please do not write "latest" as a version, specify a version number ***)
32 or 64 bit version of product:
Operating system:
32 or 64 bit OS: 5.3.130 (getting ready to upgrade to 5.3.131)

DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM

Hello, with our previous versions of PowerShell Studio when we built MSI's the location path would be C:\Program Files\Program_Name with the new version of PSS we have to input a company name and that becomes part of the install path; example C:\Program Files\Company_Name\Program_Name.

We have several scripts and reports that are based off of the 'regular' location and do not want to have to change all those. Is there a way to not include the Company Name in the MSI package deployment path?

Re: MSI Package Location & Build

Posted: Thu Dec 08, 2016 10:48 am
by DevinL
When you say that with the new version of PowerShell Studio you have to input a company name that becomes part of the install path, where exactly are you being prompted to enter this?

If you go to the MSI Package settings and navigate to the Files / Folders tab, you can choose the folder the MSI is stored when it's created.
MSI_Settings.png
MSI_Settings.png (17.21 KiB) Viewed 5364 times

Re: MSI Package Location & Build

Posted: Thu Dec 08, 2016 5:08 pm
by Alexander Riedel
Using the company name is considered a best practice for path names for installing software and its shortcuts as well as for registry names.
We apologize that this change may require a few modifications for you. In general you should not hard code paths to installed software.
I asked June Blender to put together a blog post which lists the options for retrieving the location of installed software, so you never have to rely
on a hard coded path name. Please stay tuned.

Re: MSI Package Location & Build

Posted: Tue Dec 13, 2016 7:17 am
by juneblender
Here's the blog post: How to find an installation directory.
http://info.sapien.com/index.php/script ... -directory