Posts: 9
Joined: Wed Aug 03, 2022 3:23 pm

Physical Source not updating to be relative to project file

Mon Aug 08, 2022 8:44 pm

So I have a project.aip folder in

I have two folders that I want to synchronize in my project:

(where num starts at 1 when i created the project but will increment each time we build)

I have set up my project so that folder1 and folder2 are places under the ISS WWW Root Folder. Both folders are set to synchronize. Each time we run the build our path will increment by 1. The project is set up with relative paths. I would expect that each time we clone the project to a new folder, that the physical source of the files would update itself to be relative to the new path of the project.aip file but that doesn't appear to be the case. As of now its always pointing to the folder path of when I created the project so C:\builds\build_run_1\site1\folder1 as an example. How do I get it so that the Physical Source of the files is relative to the changing path of each build of the project.aip build?

Running version: Version 19.6 (BF52C98E)

Posts: 9
Joined: Wed Aug 03, 2022 3:23 pm

Re: Physical Source not updating to be relative to project file

Tue Aug 09, 2022 7:36 pm

After lurking through the forum, I am wondering further if there is no way the project automatically changes paths of synchronized files/folders which "should be" relative to the project file path.

Looking at post: viewtopic.php?t=28487

So what would be the best recommended solution for a project with synchronized folders wanting to use relative paths for a project file that will have a unique path each run?

Posts: 5164
Joined: Wed Jun 13, 2018 7:49 am

Re: Physical Source not updating to be relative to project file

Fri Aug 12, 2022 4:11 pm

Hello Peter,

Paths are stored (in AIP) by default as *relative* to the project file (AIP), if they reside on the same logical drive as the AIP. Otherwise, they are stored in absolute form.

Check available options here: ... s-tab.html

Also, be aware, that if you use project app paths (symbolic variable paths), they may be subject to environment changes (dependent on the machine where you open the project) - this being the intended behavior. ... ables.html ... h-var.html

Project resource files policy: ... ables.html

Let me know if that helped!

Best regards,
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”