Source Path variable

[jsmith]

I am currently evaluating Advanced Installer. I've hit a snag pretty early in the going - Is it possible to specify a variable in the Source Path to a file that gets installed? Imagine I have two build configurations, Debug and Release. When I build the Debug config, I want to include the file:

..\build\Debug\bin\my_app.exe

When I build the Release config, I want it instead to include the file:

..\build\Release\bin\my_app.exe

I have created an Install Parameter - BUILDCONFIG - that is set to "Release" in the Release build configuration and to "Debug" in the debug build configuration. I'd love to be able to somehow inject this Install Parameter into the source path for my_app.exe, thusly:

..\build\[|BUILDCONFIG]\bin\my_app.exe

So that the correct version of the binary is included in the MSI. Is this possible? If not, my company cannot use Advanced Installer unfortunately.

[Cosmin]

Hi,

This could be done by using custom path variables. For example, you can try this:
- use the "Project" -> "Convert Paths" menu to launch the path variables wizard
- follow the wizard until you reach the page with the files that will use path variables
- right-click on the folder which contains the file and use the "Create Path Variable" menu
- create a custom Path Variable
- when you want to build the Debug configuration you can set the path variable to the debug path
- when you want to build the Release configuration you can set the path variable to the release path

Regards,
Cosmin

[jsmith]

Thanks for the reply. If I've read correctly, custom path variables are system wide, right? Any developer that runs Advanced Installer will have to manually set the custom paths to match his system? If I have two source control branches checked out, I'd have to alter the custom path every time I switch to the other branch? And I'd have to manually change it any time I want to build a different config? Are these things true?

[Cosmin]

Hi,

If I've read correctly, custom path variables are system wide, right? Any developer that runs Advanced Installer will have to manually set the custom paths to match his system?

Yes, this is true.

If I have two source control branches checked out, I'd have to alter the custom path every time I switch to the other branch? And I'd have to manually change it any time I want to build a different config? Are these things true?

Unfortunately yes, the path variables need to be changed every time you change the build configuration. However, I have added on our TODO list an improvement which will allow you to override a path variable for a build performed through the command line interface (it will allow you to use a specific path variable value for each build). This improvement will be available in a future version of Advanced Installer. Thank you for your suggestion.

Regards,
Cosmin

[jbabco]

has this ever been implemented? can't find it in the docs.

[Cosmin]

Hi,

I'm afraid that it has not been implemented. No other users requested this improvement, so our developers worked on other features and improvements with a higher priority. However, this is still on our TODO list and it will be available in a future version.

Regards,
Cosmin

[r_s]

I too would really like to see this implemented. We've integrated AdvancedInstaller nicely with our team build, but the path variables are different for different build types - it would be great to be able to change them even if that were via a command line call.

[GabrielBarbu]

Hello,

Thank you for suggestion. I have increased the priority of this improvement.

Best regards,
Gabriel

[bccc]

I am also having this issue and would like to see a solution.

I have tried to work around this using an environment variable to set the path variable via the option in the "Edit Path Variables" dialog. However, when I build from the command line I get an error: "Exception - File [%AI_BUILD_SRC_PATH%\Test.txt] could not be read." Is there really no way to do this without making the edit in the UI?

Thanks!

[GabrielBarbu]

Hi,

I have again increased the priority of this. The feature will be available in the near future.

Best regards,
Gabriel

[Kristoffer]

Now this was a real show-stopper. Trying to integrate advanced installer with out Continuous integration server, but this makes it difficult, if not impossible. Looking for alternative solutions in the meantime.

[bryanmanwaring]

Add me to the list requesting this feature! I am in the process of evaluating your product for our development. So far, every other aspect is great. I have to figure out how to manage this without changing the build system each time for the various builds we do. This is a must have.

[mihai.petcu]

Hello,

The feature my colleague Cosmin mentioned has been implemented by our development team and will be available in the 8.1 release which will be very soon.

Best,
Mihai

[LuWa]

Hi.

Can you tell me a concrete Release Date for 8.1 release?
Will the release be in March?

Thx

[mihai.petcu]

Hello,

Unfortunately, I cannot provide an exact date or period, however our development and test team are in the sanitation phase of the release.

Best,
Mihai