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!

Igor Markovic
Posts: 17
Joined: Wed Jan 04, 2012 1:44 pm

Improve configuration file structure to make merging easier

It would be nice if the structure of the configuration file could be cleaned up so merging different versions of the file easier. Like:
- Don't use NextFile attributes.
- Update the BuildKey attribute of the the BuildComponent (or any other Key attribute of other components) when the BuildName (or any other display name) is changed. Now we have the following XML as a result of a rename:

Code: Select all

<COMPONENT cid="caphyon.advinst.msicomp.BuildComponent">
    <ROW BuildKey="DefaultBuild" BuildName="FullSetup" BuildOrder="1" BuildType="1" PackageFolder="FullSetup" PackageFileName="Setup" Languages="en" InstallationType="2" CabsLocation="1" UseLzma="true" PackageType="1" FilesInsideExe="true" ExeIconPath="Resources\3mensio.ico" ExtractionFolder="[AppDataFolder][|Manufacturer]\[|ProductName]\install" UACExecutionLevel="2"/>
    <ROW BuildKey="FullSetup_1_1" BuildName="PatchSetup" BuildOrder="2" BuildType="1" PackageFolder="PatchSetup" PackageFileName="Setup" Languages="en" InstallationType="2" CabsLocation="1" UseLzma="true" PackageType="1" FilesInsideExe="true" ExeIconPath="Resources\3mensio.ico" ExtractionFolder="[AppDataFolder][|Manufacturer]\[|ProductName]\install" UACExecutionLevel="2"/>
    <ATTRIBUTE name="CurrentBuild" value="FullSetup_1_1"/>
</COMPONENT>

<COMPONENT cid="caphyon.advinst.msicomp.PreReqComponent">
    <ROW PrereqKey="Adobe_Reader_9.1" DisplayName="Adobe Reader 9.3" SetupFileUrl="Tools\PatchWarning.js" Location="0" ExactSize="0" Operator="1" ComLine="Adobe Reader 9.3" BasicUiComLine="Adobe Reader 9.3" NoUiComLine="Adobe Reader 9.3" Options="m" TargetName="PatchWarning.js" Builds="FullSetup_1_1"/>
</COMPONENT>
As you can see PreReqComponent also uses this build key, but it is a bit tricky as the FullSetup_1_1 is actually the Patch setup. You can also see that the PrereqKey is not updated after a rename of the DisplayName.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Improve configuration file structure to make merging eas

Hi Igor,

Thank you for the suggestions, they have been added by my colleagues from development on a TODO list for further analysis.

However, you should know that we strongly recommend to our users not to edit the projects outside of Advanced Installer, i.e. with a merging tool or any other text editor.
This often results in broken projects or, even worse, later cause other problems to appear, due to unexpected project file configurations\conversions. Even with a very good understanding of the project file layout, as in your case, mistakes can appear.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Feature Requests”