Support for Windows Mobile/CE CAB projects is available starting with version 7.0 of Advanced Installer. For more details, see the following help article.
Starting with version 7.2, Advanced Installer contains a dedicated view which greatly simplifies registering your mobile applications with the Windows CE Application Manager. For more details about this, please see the ActiveSync page help topic.
Hi Chris, The problem is caused by missing metadata in the generated CAB packages. When the CAB files are left uncompressed, CEAppMgr can determine this required information directly, but not when compression is used. Thank you for bringing this to our attention. The next Advanced Installer version ...
Hi, In a VBScript Custom Action, you can simply use the WriteToLog function described in this HowTo article : Function WriteToLog(msg) Const msiMessageTypeInfo = &H04000000 Set record = Session.Installer.CreateRecord(1) record.StringData(0) = "[1]" record.StringData(1) = CStr(msg) Session.Message ms...
Hi, Indeed, when there are several different CAB files (as opposed to the same CAB file but with different target platform settings), it is required to create separate .INI files for each and launch "CeAppMgr" with each .INI file as the argument. Starting with ActiveSync 4.5, "CEAppMgr" also support...
Hi, The string for the "CabFiles" INI key should contain no unnecessary spaces . Additionally, you should rename the CAB file for your application "ScanInOut Setup.CAB" such that it also does not contain any spaces in its name (for instance, "ScanInOut_Setup.CAB"). Therefore, the CAB_FILE Property v...
Hi Peter, You are receiving the error message because you have not configured the Data Source attributes correctly. Try to delete the "LastUser" and "Driver" attributes from the list control and let me know if the problem persists. The "Driver" attribute must not be specified because it is determine...
I could not reproduce this issue when assigning a simple MSI package to computers in our test domain. Please send the AIP file you are using to support at advancedinstaller dot com in order to investigate this issue.
Hi, Currently the attributes are extracted only when an assembly is added in the Assemblies page. This is a limitation of Advanced Installer which will be addressed in a future version. Thank you for bringing this to our attention. In the meantime, you can delete the assembly and then re-add it in t...
Hi Chris, Most likely this problem is due to a dependency issue, because the Custom Action worked correctly on my development machine. I have noticed that the DLL you have sent has a dependency on "MSVCR90D.dll" (the debug version of the VC 2008 runtime library), which might not be present on the sy...
Currently Advanced Installer does not support creating Windows CE CAB files. We are working on this feature as we speak and it will be available in a future version.
Hi, Note that the three digit limitation applies only to the value of the ProductVersion Property, not to the executable files in your package (which can have four fields in their versions). As it is mentioned in the SDK, the fourth field can be included, but it is ignored (which means that "1.2.3.4...
