Windows mobile cab file launches main executable on completion
I am developing a WinMo application where we host the cockpit files on our web server to make it easier to deploy to our handheld computers.
I would like to make a CAB file, although when the user downloads and runs it, it installs and then automatically runs the program.
I found this Q , but it seems to be about ActiveX browser add-on booths or such.
Does anyone have any ideas or instructions on how to make the WinMo CAB auto-install the primary output file after installation? I am creating a CAB file using the Smart Device CAB Setup project in Visual Studio 2008. The devices are WinMo 6.1.
Thanks in advance...
source to share
I am currently working on Windows Mobile 6.1 handheld devices. I had the same problem and luckily I was able to fix it. Please follow these guidelines carefully.
* You had to have create an XML script if you have multiple CAB files
* If you have a single CAB file than place your cab file in CABFOLDER on your
mobile unit and run AUTOCAB.EXE that can be found somewhere in your mobile unit
* If you want to work with XML script than follow this XML
enter code here
'<AutoConfig>
<Files>
<File Src="http://10.0.0.102/Softwares/XMLMultiFileDownload.zip"
Dest="\SD Card\XMLMulti12eDownload.zip"
FileId="620.121.0">
</File>
<File Src="http://10.0.0.102/Softwares/hello.zip"
Dest="\SD Card\29Sep.zip"
FileId="530.0.04">
</File>
<File Src="http://10.0.0.102/Softwares/IBI.CAB"
Dest="\CabFiles\IBI.CAB"
FileId="130.331.151.1521"
StartIn="\CabFiles"
Run="\CabFiles\autocab.exe"
CmdLine="-FILE="\CabFiles\IBI.CAB" -FORCE -SHOW=2 -CHKRST=1">
Wait="true"
</File>
<File Src="http://10.0.0.102/Softwares/DC_Net.CAB"
Dest="\Flash File Store\DC_Net.CAB"
FileId="125.734.03.0390"
Run="\2577\autocab.exe"
CmdLine="-FILE="\Flash File Store\DC_Net.CAB" -FORCE -SHOW=2-
Wait="false"
>
</File>
</Files>
</AutoConfig> '
enter code here
Note: this file must be in standard XML format
source to share
To be clear what you have now is that the CAB is downloading and installing correctly, but what do you want the application to execute after the installation is complete? In this case, add a custom installation DLL that succeeds (so CreateProcess is called in Install_Exit).
source to share