We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

lharper
Posts: 3
Joined: Wed Dec 09, 2020 1:57 pm

Physical Paths in Azure DevOps

Hello,

Very new to Advanced Installer, trying to create an MSI using a build pipeline in Azure DevOps.
I get the following error, "Resources referred by the project are missing:" (see end-of-post for full output).

I understand that the Physical source does not exist during the build pipeline, however. I really am stuck trying to resolve it.

I have tried:
Updating the Physical source using PowerShell during the build - threw XML error.
Using path variables - this only updated part of the path "C:\" and not "C:\dev\InstallerPlayground\Client\Client\x64\"

What I have not tried:
Altering the Physical source to C:\dev\x64 so that when the build runs "C:\" is replaced with "D:\a\1\a\"
(Though I don't think it should matter where the Physical Source is located on the C:\ drive as long as it points to the correct place in Azure DevOps).

Desired outcome:
That the Physical source during the build points to $(Build.ArtifactStagingDirectory)\x64 and not D:\a\1\dev\InstallerPlayground\Client\Client\x64\

Thanks for any help.


Version : 2.0.5
Author : Caphyon
Help :
==============================================================================
Downloading: https://www.advancedinstaller.com/downloads/updates.ini
Checking if a cached copy exists for this version...
Found tool in cache: advinst 17.7.0 x86
Cached copy of AdvancedInstaller exists. No need to install afresh. Cached tool location: C:\hostedtoolcache\windows\advinst\17.7.0\x86.
Prepending PATH environment variable with directory: C:\hostedtoolcache\windows\advinst\17.7.0\x86\bin\x86
C:\hostedtoolcache\windows\advinst\17.7.0\x86\bin\x86\AdvancedInstaller.com /execute D:\a\1\a\x64\ManualInstallerProject\DemoBuilds64BitMsi.aip D:\a\_temp\6768.aic
SetPackageName "DemoApp.msi" -buildname "DefaultBuild"
Build -buildslist "DefaultBuild"

Checking builds status
Resources referred by the project are missing:
D:\a\1\a\x64\ManualInstallerProject\Icons\Demo-icon.ico
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.Client.appsettings.json
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.Client.exe
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.Client.pdb
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.DemoSAS.exe
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.DemoSAS.pdb
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.LoginMonitor.exe
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.LoginMonitor.pdb
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.Server.appsettings.json
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.Service.exe
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Demo.Service.pdb
D:\a\1\dev\InstallerPlayground\Client\Client\x64\DemoSAS.appsettings.json
D:\a\1\dev\InstallerPlayground\Client\Client\x64\DemoSAS.dll
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\LICENSE
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\LICENSES.chromium.html
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\chrome_100_percent.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\chrome_200_percent.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\d3dcompiler_47.dll
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\ffmpeg.dll
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\icudtl.dat
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\learners-relay.exe
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\libEGL.dll
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\libGLESv2.dll
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\am.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\ar.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\bg.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\bn.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\ca.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\cs.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\da.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\de.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\el.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\en-GB.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\en-US.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\es-419.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\es.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\et.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\fa.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\fi.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\fil.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\fr.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\gu.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\he.pak
D:\a\1\dev\InstallerPlayground\Client\Client\x64\Relay\locales\hi.pak
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Physical Paths in Azure DevOps

Hello,

Please take a look on the "Support for moving AI Project file" thread which should help you.

If you want to update a path variable from the command line you can use the "/UpdatePathVariable" command.

Let me know if you have other questions.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”