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!

brucer
Posts: 5
Joined: Tue Nov 23, 2004 12:30 am
Location: Palo Alto, CA
Contact: Website

Command Line Enhancement

We use the command line interface to build the installer.

We would like to update the version number and other content
in the xml file, but a new ProductCode needs to be
generated, so the GUI interface needs to be run to manually
force this update.

Can a command line interface be provided to update this?

Here's one scenario for how we would like to use Advanced Installer:

* Use the GUI to define the dialogs, and the files needed for the
install. I.e. setup the main structure and the initial content.

* Use an xslt tool to parse the *.aip file and our
version.xml file to update the content of selected tags in
the aip file. For example, we probably would only change
these tags:

Code: Select all

    ROW Property="ProductVersion" Value="n.n.n"
    ROW Property="ProductName" Value="foo"
    ROW Property="Manufacturer" Value="foo, inc."
    ROW Property="ARPCONTACT" Value="email@com"
    ROW Property="ARPURLINFOABOUT"  Value="short desc. text"
    ROW Property="ARPCOMMENTS" Value="longer desc. text"
* Call the advanced installer command line with a flag, to
update these values (perhaps the output file is also
specified):

Code: Select all

    ROW Property="ProductCode" Value="
    ROW Property="UpgradeCode" Value="
* Now the advanced installer command line would be run to make
the installer.
Cata
Posts: 638
Joined: Thu Apr 10, 2003 7:37 am
Contact: Website

Changing the XML file directly is dangerous. There is a whole lot of thing going on under the hood when you change something. Validity checks, etc.

For the version, a new Product Code must also generated, if you want the "automatically upgrade older versions" to work.

Our solution, which we are working on, is to offer a command line interface to the most common operations from the UI. Like:

advinst.exe /prj foo.aip /setversion 1.2.3 -newProdId

or

advinst.exe /prj bar.aip /addfile c:\temp\foo.txt TARGETDIR\MyFiles

Cata
Catalin Rotaru - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Guest

When

setting the version in a command line build is very important for us.
When will you have it?
Also we would like to set properties.
Regards
Hans
[Currently evaluating]
Cata
Posts: 638
Joined: Thu Apr 10, 2003 7:37 am
Contact: Website

Hi Hans,

Setting the version from the command line is already available in Advanced Installer. Read about it at:

http://www.advancedinstaller.com/user-g ... iting.html

What properties would you like to change from command line? Can you please give an example?

Thanks!
Cata
Catalin Rotaru - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rhdegc
Posts: 4
Joined: Tue Oct 24, 2006 12:15 am

setversion does not modify product code

When seeing a modification in the the revision code (0.0.0.xxxx), setversion changes the version, but does not update the product code. So going from 5.7.0.1202 to 5.7.0.1203 does not change the product ID.

This makes automatic update deployment a lot more difficult - can it be fixed soon?
rhdegc
Posts: 4
Joined: Tue Oct 24, 2006 12:15 am

temp fix

By resetting the version using /SetVersion 1.0 before running SetVersion /fromfile for the incremented build, I guarantee a change in product code. Not ideal if there was not actually a change, but it temporarily solves my pushout problem.
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

Note that the fourth field of the "Product Version" is ignored by Windows Installer and changing it alone does not generate a new package.

The /SetVersion command automatically changes the "Product Code" (if the old version is different from the new one) unless the -noprodcode options is used. For more details about /SetVersion command please see:
http://www.advancedinstaller.com/user-g ... rsion.html

Best Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
stevefal
Posts: 119
Joined: Wed Sep 03, 2008 9:02 pm
Location: Washington USA
Contact: Website

Re: Command Line Enhancement

I am also using the workaround above - SetVersion 1.0 before setting the version from file.

Since Visual Studio automatically increments build number only once per day, this workaround lets me test multiple revisions of the same build within a day, without uninstalling first. Revisions are treated as upgrades even though the build number is the same.

Are there are any negative consequences to using this approach?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Command Line Enhancement

Hi,
Are there are any negative consequences to using this approach?
I don't think there are any.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
stevefal
Posts: 119
Joined: Wed Sep 03, 2008 9:02 pm
Location: Washington USA
Contact: Website

Re: Command Line Enhancement

Actually, that approach seems to cause multiple versions of the same app to show up in Add/Remove Programs. In my .NET scenario, it also appears to create a kind of assembly-hell situation.

ABORT!
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Command Line Enhancement

Hi,

Please note that this shouldn't happen if you are using the automated upgrade feature. When installing a new version the old ones should be uninstalled automatically.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
stevefal
Posts: 119
Joined: Wed Sep 03, 2008 9:02 pm
Location: Washington USA
Contact: Website

Re: Command Line Enhancement

I am using the automated upgrade feature, but I quite consistently got multiple instances of my app in Add/Remove Programs, on more than one machine, when using "/SetVersion 1.0" before using "/SetVersion -fromfile", where the resulting version number was the same as before.

I've solved my problem by using a Visual Studio macro that reliably increments build number upon every Release build, and I've removed the /SetVersion 1.0 switch from my AI script.

Return to “Feature Requests”