Migrating from 12.3.1 to 12.8 has path problems - Advanced Installer Community
thill
Posts: 111
Joined: Sat Jan 21, 2012 5:58 pm

Migrating from 12.3.1 to 12.8 has path problems

I'm upgrading several projects from 12.3.1 to 12.8, as well as a few other changes. It would appear there are migration problems.

To do this work I created a gitHub feature branch and cloned it to a different path than the master project. So the path changed. But now I cannot get it to build.

Questions:
1. Did a Convert Paths on each project in 12.3.1 before migrating to 12.8 and made sure ALL paths had a Project Variable.

2. If AI removes files because of path issues, then re-adds them, they get new UUIDs. That will cause upgrade problems won't it?

3. When building from the command-line it shows the error "The source folder D:\staging\dovue" of the synchronized folder "APPDIR" is missing from disk. ...". But that Project Variable is actually D:\git\docvue\dve\installers\staging\docvue and it resolves correctly in AI interactively. The project root is D:\git\docvue\dve\installers\projects. And the project is set to use relative paths. Why can it not resolve the same paths when run from the command-line???

4. I cannot seem to save Path Variables (Project Variables) to a file anywhere. I go through the motions but no file is ever written to the path displayed in the dialog. Even to the directory containing the project's .aip file. And it's the same with 12.3.1, 12.7.2 and 12.8. There are only 2 "Project Variables", which are in the .aip, and no Custom Variables. Is that why no file is produced? How does that actually work?

Observation: Looking in the 12.3.1 .aip file it had relative paths for caphyon.advinst.msicomp.AppPathsComponent like ..\staging\docvue. But after building from the command line with 12.8 that path turned in to ..\..\..\..\..\..\staging\docvue which is the root of drive D:. Seems like a bug!

5. We use TeamCity + GitHub for automated builds in a dynamically-generated directory (on C:). AI is executed from an ant build.xml. And we use that same server to AI development on a separate hard drive than where TeamCity runs. How can paths be handled for those 2 situations? This wasn't an issue with 12.3.1, but 12.8 fails with path problems.

At this point we cannot build successfully.

Another question:

a. Organization with added files: We added a JRE to the root directory, e.g. APPDIR/jre. And our product has features with subfeatures. When AI scans for additions it places hundreds of new entries in the root of a feature, not the designated Current Feature. That requires long painful movement of each individual entry to the correct subfeature so if the user does not choose to install everything it is in the right place. Why does it not use the Current Feature when adding new files??? Is there any way to avoid moving hundreds of entries by hand??

I will email the primary project file to AI support.
thill
Posts: 111
Joined: Sat Jan 21, 2012 5:58 pm

Re: Migrating from 12.3.1 to 12.8 has path problems

A little more information:

Today I reverted to the project files used with 12.3.1 and got them to build successfully.

Without changing a thing re-ran those builds with 12.8 and they all fail with: The source folder "D:\staging\docVue" of the synchronized folder "APPDIR" is missing from disk. You need to either recreate the source folder path or reset the synchronization from the "Folder Properties" dialog, in "Synchronize" tab.

Again, \staging\docvue is several directories down in our git directory structure.

When this happens the 12.3.1 AppPathsComponent goes from:

Code: Select all

  <COMPONENT cid="caphyon.advinst.msicomp.AppPathsComponent">
    <ROW Name="prestagedInstaller" Path=".." Type="2" Content="0"/>
    <ROW Name="resourcePath" Path="..\images" Type="2" Content="0"/>
    <ROW Name="stagedDocvue" Path="..\staging\docVue" Type="2" Content="0"/>
  </COMPONENT>
To 12.8:

Code: Select all

  <COMPONENT cid="caphyon.advinst.msicomp.AppPathsComponent">
    <ROW Name="prestagedInstaller" Path="..\..\..\..\..\.." Type="2" Content="0"/>
    <ROW Name="resourcePath" Path="..\..\..\..\..\..\images" Type="2" Content="0"/>
    <ROW Name="stagedDocvue" Path="..\..\..\..\..\..\staging\docVue" Type="2" Content="0"/>
  </COMPONENT>
We do a few things during a build:

Code: Select all

AdvancedInstaller.com myproject-setup.aip /SetCurrentFeature ServerFeature
AdvancedInstaller.com myproject-setup.aip /SetVersion 10.2.5.9425
AdvancedInstaller.com myproject-setup.aip /SetProperty SOFTWARE_VERSION=9425
AdvancedInstaller.com myproject-setup.aip /SetProperty BUILD="10.2.5 05/12/16 9425"
AdvancedInstaller.com myproject-setup.aip /SetProperty SEQ=9425
AdvancedInstaller.com myproject-setup.aip /SetProductCode -langid 1033
AdvancedInstaller.com /rebuild myproject-setup.aip
Is there anything wrong with any of that?

Could one of those be causing the path problem?

Thanks!
thill
Posts: 111
Joined: Sat Jan 21, 2012 5:58 pm

Re: Migrating from 12.3.1 to 12.8 has path problems

I have confirmed the problem discussed above ... that the paths to things get changed to long ..\..\..\..\....... with 12.8.

Any thought on how to proceed?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Migrating from 12.3.1 to 12.8 has path problems

Hello Todd,

I've tested your project conversion scenario in a test project, but I cannot replicate the issue at all. The project path variables are always preserving their paths in the upgraded project (from AI 12.3.1 to AI 12.8). I'm not sure why this happens on your side.

Would you please try to recreate this issue in a new test project having a similar configuration with your original project? This will be very useful for us in order to investigate the behavior. If you could send us a a download link for a buildable sample (AIP v12.3.1 + its referenced resources) which replicates the behavior to support at advancedinstaller dot com this will be great too.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
thill
Posts: 111
Joined: Sat Jan 21, 2012 5:58 pm

Re: Migrating from 12.3.1 to 12.8 has path problems

Had an idea and just tried it - was successful. The problem came from our Ant build.xml using a relative Basedir. To explain in case someone else runs across this problem ...

Our Ant build.xml runs Advanced Installer in a procedure on TeamCity. The old line was:

Code: Select all

<property name="installer.dir" value="."/>
This problem was solved by changing that to:

Code: Select all

<property name="installer.dir" value="${basedir}"/>
Something about the dot .\ relative path caused Advanced Installer to expand relative paths in the .aip file to full paths from the root of the hard drive, e.g. it would take ..\images and expand it to ..\..\..\..\..\..\images. We develop on the D: drive of the Windows server running TeamCity. But TeamCity itself runs on C: in a shorter directory structure so those paths of caphyon.advinst.msicomp.AppPathsComponent would be pointing to the wrong place.

By giving Advanced Installer a fully-qualified path to the .aip file directories were handled differently.

For reference, this is how Advanced Installer is executed, along with a few other property sets:

Code: Select all

<property name="installer.dir" value="${basedir}"/>
<property name="installer.projects.dir" value="${installer.dir}/projects"/>
<property name="installer.exe" value="C:\Program Files (x86)\Caphyon\Advanced Installer 12.8\bin\x86\AdvancedInstaller.com" />
<exec executable="${installer.exe}">
    <arg line="/edit ${installer.projects.dir}\product-setup.aip /SetProductCode -langid 1033"/>
</exec>
<exec executable="${installer.exe}" dir="${installer.projects.dir}">
    <arg line="/rebuild product-setup.aip"/>
</exec>
I think it may have been the SetProductCode or similar run of AI using the path ".\projects\product-setup.aip" that caused the ..\..\.. expansion - but of course that's just a guess. Changed all AI runs to the second form of syntax so paths with spaces are handled well.

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

Re: Migrating from 12.3.1 to 12.8 has path problems

Hello Todd,

I'm glad you solved this out. Thank you for sharing with us the solution.

If there is anything we could assist you with just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”