Welcome to the Indigo Rose Software discussion forums! You will need to sign up for a forum account and login before you can post. Need help? View the Forum FAQ.
The same approach that Josh gave here would work. However you should note that, if you reinstall the product using a different version number in the shortcut of the Control Panel, you will be creating a new shortcut instead of overwriting the existing one. For this reason it might be best to suppress the number completely - or you must perform an automatic uninstall before installing the other version. You should avoid stuff like this:
You can also use my FileVersion utility, or tools like Kinook's Visual Build to extract the version number and pass it to Setup Factory as a build constant.
How can I do if i build a new version, for example from 1.0 to 2.0, in the ad or remove programs is a new link for the new version but a need to be autoupdated
Here's a little code snippet that I use in most of my installers.
Typically; you change the version # in SUF to reflect a new version of your installer.
What if you want this version to auto-update with your main application file?
Put this in an included LUA script file or global functions:
Code:
function SetupData.GetInternalFileVersion( cFileName )
local tFiles = SetupData.GetFileList(ARCHIVE_LIST);
local cVersion="0.0.0.0";
if type(tFiles) == "table" then
local x;
for x = 1, Table.Count(tFiles) do
if String.CompareNoCase(tFiles[x].FileName, cFileName )==0 then
cVersion = tFiles[x].FileVersion;
break;
end
end
end
return cVersion;
end
Leave a comment: