Centralized repository in a floating license Env - Advanced Installer Community
thorsten
Posts: 7
Joined: Thu Oct 30, 2014 11:29 am

Centralized repository in a floating license Env

Hello All,

currently I'm integrating AI in our development system / build process. We are using the floating license model.

The AI setup projects are stored in our version control system (VCS) beside our software projects.
Some setup projects need to install prerequsites on the target machine. These are stored in the repository(path).

I suppose, that the AI setup compiles / runs on any developer/build machine, because relative paths are used only.
Regardless of the used OS (e.g. WinXP, Win7).
The project tree has been checked out of the VCS, previously.

And there ist the problem. .. with the prerequisites!

You can setup a repository path in AI as per machine setting (pointing to "C:\ProgramData\Caphyon\Advanced..." or "C:\Documents and Settings\All Users...")
But on the other hand you have to setup the "File Path" in "Prereuisites: <Prereuisite>|Setup Files|Main Setup File" as per project setting.
This will store an absolute path (pointing to repository) in the AI project file.

And this setting makes it difficult/impossible to have an "portable" AI project, if you having different repo. paths

I expected an AI env variable like AI_REPOSITORYPATH, which ist stored like "[|AI_REPOSITORYPATH]\.NET Framework 3.5 S\dotnetfx35.exe" in the project file?!

... or is there a mistake in my thinking?

Hint:
The prerequisites should be not stored in the VCS, which could be a solution but possibly blow up our VCS with gigs of data.

Regards,
Thorsten
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Centralized repository in a floating license Env

Hello Thorsten,

Indeed, we don't have support to use path variables for source files of prerequisites. This improvement is on our TODO list and we'll notify you as soon as it will be out.

However, I'm not sure I completely understand your project configuration. If your prerequisites are added in your project from Repository, then the prerequisites source files should be found and referenced in your project from Repository too. When moving a prerequisites to Repository, Advanced Installer saves on local machine the prerequisite settings and the prerequisite source file into a subfolder created in the Repository path. Then, when moved on another machine the project file should search the prerequisite (including the source file added in "Setup" tab) in the Repository path of the current machine. Do you encounter a different behavior when using prerequisites from Repository? If so, can you please try to iterate a detailed step by step test case which we can follow in order to replicate the issue?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
thorsten
Posts: 7
Joined: Thu Oct 30, 2014 11:29 am

Re: Centralized repository in a floating license Env

Hello Daniel,

sorry for the late reply.

I will try to reproduce the steps:
  • assuming there is a setup project which needs a prerequisite... Let's say: ".NET Framework 3.5 SP1"
  • the according package ist already stored in the (central) repository
  • the repository manager points to... Let's say: Options -> Repo. Manager -> Location|Path: "C:\Repository"
  • now add prerequisite to your setup project:
    Prerequisites: Packages -> Context Menu: Add From Repository -> ".NET Framework 3.5 SP1"
  • the prerequisite item is added under the node Pre-Install . Location is: "Use files from disk" (default).
    Under the tab "Setup Files" you will see the "Main Setup File" | "File Path". It points to "C:\Repository\...<your prerequisite>"
    And this setting is stored in your setup project file (Problem!)
If you edit this setup project on another devlopers machine, and the Repository Managers path is configured to somewhere else (e. g. Z:\Caphyon\Repository) you won't be able to build this setup.
Reason: Above mentioned "Main Setup File" | "File Path" (part of setup project) points to "C:\Repository\...<your prerequisite>", which can't be found.

For me, it seems that the Repository Managers File path is only relevant, while I am adding a prerequisite to my project.
From then, the prerequsites location is stored in my project now. The project won't be portable :-(

I expect, that no explicit (absolute) path location ist stored in the setup project.
In order to still find the prereq. package, the path should be built up by a combination of "Repository Manager" - Path & relative path of the prereq. itself.
Like: "[|AI_REPOSITORY_PATH]\Prerequisites\.NET Framework 3.5 S\dotnetfx35.exe"

Please correct me, if I am wrong.

My current workaround is, specifying a common network share to our centralized repository. Like: "\\buildserver\Caphyon\AI_Repository".
This ensures that both paths starts always in the same way.

Regards,
Thorsten
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Centralized repository in a floating license Env

Hello Thorsten,

I'm not sure why this happens. Can you please make sure the related prerequisite is added into your project from Repository (using "Add From Repository" context menu option)?

I've tested the scenario using AI 11.6.3, but I cannot replicate the behavior. I've attached a sample containing a project which includes a prerequisite added from Repository which can be successfully edited and built on another machine. Can you please copy the "SamplePrereq" folder on your Repository prerequisite location, and then try to open and build the "Installation Project\Sample.aip" project file and see if everything goes fine?
sample.zip
(485.93 KiB) Downloaded 244 times
All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
thorsten
Posts: 7
Joined: Thu Oct 30, 2014 11:29 am

Re: Centralized repository in a floating license Env

Hello Daniel,

I've tried your Sample Project.
For me it is... it was :-) working.
Then I took a look into the sample.aip. I was wondering, why there is no absolute path specification for the "SamplePrereq".
In our projects we use the "Folder" setting (together with "Use files from disk" option):
sample_sshot.png
sample_sshot.png (112.33 KiB) Viewed 4275 times
Reason is, to store all needed prereqs. into one folder. Like:

Code: Select all

-+-[Prerequisites]
 | +-[Prereq_A]
 |   +-...
 | +-[Prereq_B]
 |   +-...
 | +-[Prereq_XYZ]
 |   +-...
 +-Setup.msi
 +-Setup.exe
As soon as I fill out this field ("Folder"), an absolute folder/file location is written to the project file (points to repository).
If you move this project to another machine with a different repository folder/path, it will fail at build time.

I included the modified Sample project:
sample_thorsten.zip
(478.35 KiB) Downloaded 211 times
What ist the correct intend of the "Folder" setting (together with "Use files from Disk")?

Regards,
Thorsten
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Centralized repository in a floating license Env

Hello Thorsten,

Please keep in mind this is our default behavior. After adding a prerequisite from Repository (using the "Add From Repository" context menu option) it is added into your project with all its settings stored in the Repository. However, afterwards if you edit any of the prerequisites settings (e.g. the "Folder" field), then the prerequisite package won't be referred from the Repository anymore. After the edit operation the prerequisite will be considered a new one and, thus it will be referenced with an absolute path. This is our default implementation.

Since, currently don't have path variables support for source files of prerequisites, then in order to maintain the project portable you should not edit any prerequisite settings after it is added from Repository in your project. Otherwise, you should manually set the prerequisite source files after moving the project on a new machine. I've increased the priority for including path variables support in our "Prerequisites" page too and, hopefully this improvement will be available soon. We'll notify you as soon as the enhancement is out.
What ist the correct intend of the "Folder" setting (together with "Use files from Disk")?
This folder specifies the folder name where the prerequisites setup files will be extracted/downloaded at install time. By default, all prerequisite setups are downloaded in the path specified in "Prerequisites page -> Packages tree node -> Download/Extraction folder" field (e.g. [AppDataFolder][|Manufacturer]\[|ProductName]\prerequisites). If you also set a value in the "Folder" field (e.g. MyPrereq), then your prerequisite setup will be extracted at install time in the
[AppDataFolder][|Manufacturer]\[|ProductName]\prerequisites\MyPrereq location.

If you have any questions just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Centralized repository in a floating license Env

Hello,

Several improvements have been added to our Path Variables support in version 12.5 of Advanced Installer released on October 21st, 2015.

Using the Path Variable Wizard you can convert the path for: Prerequisites, Digital Signature, Slideshow Images, SSRS Resources.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”