I use the VS2K3 Setup projects to deploy my CABs onto a dektop machine
along with little EXEs and SETUP.INIs to launch CeAppMgr and push them
onto the WinCE device. Also puts shortcuts in the Start Menu.
I use CE Cab Manager to discover and check the syntax of CabWiz's
*.inf files.
I write the infs by hand (at the moment, hope to write code to do it
soon) and have a seperate project that builds after the main project
and has a pre-build event (Build the cabs batch file). This was, a
release build of the project automatically spits out a great big MSI
file ready for shipment.
It's kinda hard work to maintain (lots of hardcoded paths in the inf
and batch files), but it means I can crank out a release pretty
quickly. Again, hopefully I will be able to turn my dummy seperate
project into a bat/inf/cab builder one day.
I chose this route because we use an automated build system, and because the
XML API was a lot easier for to work with the MSI API versus tinkering with
Orca or Installshield. I just tack on a CustomAction for running InstallUtil
to get my CAB files installed on the mobile device. I wouldn't say it's as
easy as NSIS or xcopy, but you do get a nice Windows Installer package.
Thanks to James and Ken for the other suggestions. I'm not doing any
in-house development, just small shareware apps, so I think a setup
system like EZSetup (freeware from spb) is ideal. Thanks again to
peter for that.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.