Hi Mr. Krueger and all,
I have an MSI Install Script package that installs data sets, the installs
are identicial but the data is not so I am looking for a way to have a
single code base where I can change the Product, package and/or upgrade codes
during the package build , via info from an include file, in my install
script, thus produce a unique install package for each data set.
I have tried the following but is fails to work
// set the guid for this installation
PID_REVNUMBER = 9;
MsiGetActiveDatabase(phDatabase);
// Obtain a handle to the summary information stream database by
calling the
MsiGetSummaryInformation(phDatabase,"",0,phSummaryInfo); //
function.
//Call the
MsiSummaryInfoGetProperty(phSummaryInfo,PID_REVNUMBER,puiDataType,
piValue,pftValue,szValueBuf, pcchValueBuf); // function to view a single
summary information property.
//Call the
MsiSummaryInfoSetProperty(phSummaryInfo,PID_REVNUMBER,puiDataType,0,pftValue
,newGuids); // function to set a single property
MsiCloseHandle(phSummaryInfo);
MsiCloseHandle(phDatabase);
Is there any other and hopefully simpler way of changing these guids from
within the install script itself?
Thank you
John D. Cooper
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Change ProductCode property from Installscript
Started by
gwolfjdc
, Feb 10 2005 19:48
3 replies to this topic
Posted 10 February 2005 - 20:31
I'm not sure I understand your question.
Your InstallScript will be executed at install time (when your setup runs), not at build time.
One option would be to use Product Configurations and Release Flags to build multiple packages (with different codes) from one project.
Another option would be the use of the InstallShield automation interface to modify the .ism project file from a build script for instance.
Your InstallScript will be executed at install time (when your setup runs), not at build time.
One option would be to use Product Configurations and Release Flags to build multiple packages (with different codes) from one project.
Another option would be the use of the InstallShield automation interface to modify the .ism project file from a build script for instance.
Stefan Krüger
InstallSite.org twitter facebook
Posted 11 February 2005 - 16:35
I saw this confirguation specification stuff, But I am unsure how to create different product confirurations, please advise!
Posted 11 February 2005 - 19:30
Did you read the help topic about Release Flags?
Stefan Krüger
InstallSite.org twitter facebook