Actually the Installer framework I used was customised i.e. the source code of the QTIFW was modified to suit the need and then the required QTIFW binaries are rebuilt from the modified source.

@SamiN This seemed to be quite straight forward to solve. I created my shortcuts under user desktop area, but when running maintenance tool from service using qtservice it most probably didn't have that 'user' setup in place so trying to add shortcut to desktop failed. Changed location of the shortcut to c:\users\public\desktop seems to help on this one. Br, -sami

I wonder if you ever found an answer to this issue ? I have a similar requirement, in that I want to create an online installer that works both ways. It needs to be able to be run in "download-only" mode (no installation, just download the repo). Then my client's IT dept can have a copy of the repo to put on their server, and their users (some of whom don't have internet access) can do a local installation from their local repo. It seems that most of the functionality exists: The offline installer will create a local repo if asked to (CreateLocalRepository in config.xml). This could then be relocated to their server. The online installer can be forced to act like an offline installer by pointing it the local repo. What I can't seem to do is combine 1 and 2 in the same installer. I could create both an offline and an online installer (one for client's IT and one for their users), except that I cannot package all components into the offline installer because some are licensed, and the client should only have access to the components that they have a licence for.

@Tsherr Hello, I have the same issue, tell me please, did you found solution for this problem?

It is apparently a replace and an escape issue. component.addOperation("CreateShortcut", "@TargetDir@/ArramgeApplication.exe para1 para2", "@StartMenuDir@/Arrange Application.lnk", "workingDirectory=@TargetDir@", "iconPath=@TargetDir@/Manager.exe"); Creates the installer and creates also a link and adds the two parameters. component.addOperation("CreateShortcut", "@TargetDir@/ArramgeApplication.exe @TargetDir@ para2", "@StartMenuDir@/Arrange Application.lnk", "workingDirectory=@TargetDir@", "iconPath=@TargetDir@/Manager.exe"); Creates the installer, but fails when trying to create the lnk.

It can indeed, see here: http://doc.qt.io/qtinstallerframework/ifw-online-installers.html

@koahnig I am using 2.0.1

You can use "UNDOEXECUTE". For example: component.addOperation("Execute", "msiexec", "/i", "xxx.msi", "/quiet", "UNDOEXECUTE", "msiexec", "/x", "xxx.msi");

Add this repo into MaintenceTool: http://download.qt.io/online/qtsdkrepository/windows_x86/root/qt/

@SGaist Yes, you are right. Was not really obvious to me. Here is an updated version of the config.xml of the online example of installer framework <?xml version="1.0" encoding="UTF-8"?> <Installer> <Name>Online Installer Example</Name> <Version>1.0.0</Version> <Title>Online Installer Example</Title> <Publisher>The Qt Company</Publisher> <!-- Directory name is used in component.xml --> <StartMenuDir>Qt IFW Examples</StartMenuDir> <TargetDir>@HomeDir@/IfwExamples/online</TargetDir> <!-- Change required to have English as startup language e.g. when you have an OS with German as standard language --> <Translations> <Translation>en.qm</Translation> </Translations> <!-- End of change for translation --> <RemoteRepositories> <Repository> <Url>http://localhost/repository</Url> </Repository> </RemoteRepositories> </Installer> The installer starts then with all text in English. Tested on Windows 7 64bit with German as local language.

Solution: Controller.prototype.IntroductionPageCallback = function() { // Installer is "updater" when it is run with "--updater" // or Controller does "installer.setUpdater()" if (installer.isUpdater()) { var widget = gui.currentPageWidget(); // Same as gui.pageById(QInstaller.Introduction); widget.findChild("UpdaterRadioButton").checked = true; // Disable paint events on these widgets, through the QWidget::updatesEnabled property. // I tried with the "visible" property, but it is not enough, because for some reason // that property gets reset under some conditions. For example, if "Next" button is pressed // and no updates are available. widget.findChild("PackageManagerRadioButton").updatesEnabled = false; widget.findChild("UninstallerRadioButton").updatesEnabled = false; } }