You can't use WiX. Windows Mobile uses CABs which are built with CabWiz.exe, not MSIs. You write an .inf file to tell CabWiz.exe what to do. If building only for Windows Mobile 5.0, you can use a compressed CAB and should build it with the version of CabWiz from VS2005 (typically in C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SDKTools); if you need to support Windows Mobile 2003 Pocket PC, you need to build an uncompressed CAB and build it with the older tool from the Pocket PC 2003 SDK (typically in C:\Program Files\Windows CE Tools\wce420\POCKET PC 2003\Tools).
VS2005 has a user interface for building CABs: in the New Project dialog, select Other Project Types, Setup and Deployment, Smart Device CAB Project. This UI is very similar to that used for VS2005 MSI setup projects. I'm a 5-year veteran of Pocket PC/Windows Mobile projects, and am used to simply editing an .inf file from a previous project, so I've not used this feature of VS2005. I believe it's possible to export the .inf and therefore run CabWiz in an automated build. Now, if you already _have_ a CAB file, you can use Windows Installer to install the CAB file on the PC and associate it with ActiveSync, so that it appears in ActiveSync's Add/Remove Programs list. You need to write an .ini file which describes the CAB, then pass that to the CeAppMgr.exe program. If you don't specify any flags, the CAB will be immediately downloaded to the connected device, if present, or scheduled to install on the next device that is connected. To register only, and not download, specify the /register switch. For more on how this works, see http://msdn2.microsoft.com/en-us/library/ms847066.aspx. Note that Application Manager will only work correctly if the installing user has administrative privileges - all applications are registered under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services\AppMgr\Apps (but you should not rely on this - use the supported method of running CeAppMgr.exe). I imagine that you should use a RegistrySearch to find the path to CeAppMgr.exe, and a type 34 custom action to actually run it. I'm not that familiar with how this works (the documentation for <CustomAction> really needs to be broken down into examples for each different type of custom action because it's clear as mud right now). -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Sion Sent: 18 January 2007 10:27 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX and PocketPC installations Hi there, I am at the point of creating an installer for the Windows Mobile 5 application that we have developed. I have been experimenting with WiX 3.0 to create a PocketPC installer but have been unsuccessful. Could anyone shed some light as to how I use WiX to generate an installer for PocketPC? If this is not possible does anyone know of another tool that can create PocketPC installers AND be integrated into a build environment outside Visual Studio? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
