This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Adrien
Level 4
‎May 03, 2018 11:10 AM

Cache path for packages in suite projects

Hi,

Installshield 2018 includes prerequisite for SQL Server 2014 Express SP2. I use this prerequisite in a Suite Project.

During the installation of this Suite Project, SQLEXPR_x64_ENU.exe is extracted in %localappdata%\Downloaded Installations\{GUID}. On some machines, probably depending on the length of the Windows account name, the SQLEXPR_x64_ENU.exe installation failed with the following error:

SQL Server installation media on a network share or in a custom folder can cause installation failure if the total length of the path exceeds 260 characters. To correct this issue, utilize Net Use functionality or shorten the path name to the SQL Server setup.exe file.

(the error is the same when starting the installation outside the Suite Project)

To work around this problem, I have to change the cache path of the SQL Server package. I can use:
- Other locations like WindowsFolder, CommonDocuments... none of these folders suit me.
- A hard-coded value: it's very dirty.
- According to the InstallShield help, a formatted expression that contain a property name: perfect, that's what I need!

InstallShield help wrote:
When you type a value for this setting, you can include one or more formatted expressions that contain property names, environment variable references, and other special strings; at run time, the installation expands the values of these expressions.


Unfortunately, when I apply a custom property to the package cache path (ie: [MyProperty]), I get the following error:

Invalid path entered. Make sure you enter a valid folder location.

So... is there a way to use a property as a cache path, initialized by the user or a custom action?

Thanks for help!

Adrien
Labels (1)
Labels
0 Kudos

(2) Replies
DLee65
Level 13
‎May 08, 2018 09:37 AM

I replicated the behavior. I am able to get around it by opening the suite project in Notepad++ and editing the value manually. The test project compiles successfully.
0 Kudos
Adrien
Level 4
‎May 09, 2018 04:48 AM

Wow, it works like a charm, thank you very much!

For those who would have the same need, simply save your Suite Project with a package cache path that you can search easily (ie: [LocalAppDataFolder]Downloaded InstallationsXXX). Then:

[LIST=1]
  • Open your .issuite file in a text editor.
  • Search your custom cache path. You will see something like this:
    [CODE]






    [/CODE]
  • Update this path as needed (ie: Name="[MyCachePath]").
  • That's all. If you reopen your Suite Projet, you can see [MyCachePath] as cache path for this package.
    Nice trick, thanks again 🙂

    Adrien
    • 0 Kudos