Reading version info from a file

[jkpieterse]

Hi,

Tried searching for the anwer first, but didn't find it, so here goes:

What would it take to have SUF version 7 read an external file to set some session variables like %ProductVer% prior to showing the first install screen, so the setup session uses those variables?

[Ulrich]

Hello,

I think it is best if you set these variables at build time. When you build your installer, you would check the version info of the file you are including in the setup, and set a build constant. By doing so, you can include that info in the installer resources and screens.

There are several tools you can use for this, my preferred is Kinook's Visual Build. It can scan the application's project file and extract the FileVersion directly from the resources. Then you can use that info to set a build constant in an INI file used by Setup Factory. Otherwise, you can use a tiny tool I published here before: FileVersion tool for Setup Factory

You can download the utility from here.

Ulrich

[jkpieterse]

Hello,

I think it is best if you Then you can use that info to set a build constant in an INI file used by Setup Factory.

Thanks for your reply.
Could you perhaps tell me where I can find information as to how to read an ini file in SF v7 scripting and what the exact content of the ini file must be to comply?

[Ulrich]

You can find a sample of the INI in the post I pointed you, and it is also well documented in the help file. Look for "unattended builds" and "command line options" in the help. You don't need to read the INI file at all with scripting, and the file will not be included into the finished setup.

Ulrich

[jkpieterse]

Thanks. I obvioulsy misread your post. HAd a closer loook and this is what I need indeed.
Thanks again.

[jkpieterse]

Hi Ulrich,

Revisiting and re-reading this subject now.
You appear to have misinterpreted my question after all (which is likely caused by me not explaining too well what I want).

Your solution enables one to have SUF build setup files with "dynamic" build constants read from a file. It requires SUF.

However, what I am after is the possibility to build a setup file, which includes an ini file of some sort (or a simple plain text file). When the user runs the setup.exe, the setup reads the textfile and adjusts the setup settings accordingly. This would enable me to:

Generate ONE setup file, which has no files included in its package, just references.
Re-distribute a new build of a tool by simply editing the textfile to update the build number and zip all files in the setup folder to get a new setup package.

In other words, I only need SUF to set everything up and create the setup.exe. After that, I can stay out of SUF and just update a textfile and drag in some new versions of the package.