JamesFielding
Wed Dec 13 00:07:01 CST 2006
> Of course, [InstallShield] costs about $1100 and Windows Installer
> technology comes with VS.Net 2003, so you have to factor that in.
Alternatively, for about $75, you can try "PocketPC Installer" at
http://www.pocketpcinstaller.com
This is incredibly easy to use.
You just drag'n'drop your .cab and data files into the program,
and it'll compress them into *two* types of compressed,
standalone .exe installer files.
One runs on your PDA. So you could put this one "autorun.exe"
file on a memory card, and distribute your app this way. All the
user would need to do is to insert the memory card into their
device, and sit back and watch for a few minutes !
The other installer runs on your Desktop. This *also* contains
compressed copies of all of your files. It will search for a device
connected to your PC, then deploy the install package (contained
within the installer.exe file) to your device, then start installing
it.
Two different ways of deploying your app, just choose which
of the two is more useful for you.
There are a load of useful options, see the website for
details. And the 30-day demo lets you see it all in action.
Best regards,
James
"Darren Shaffer" wrote:
> No special code required - both installer technologies know how to register
> a package with Activesync to be deployed upon next sync. My experience
> using both the Windows Installer option and the Installshield option is that
> the InstallShield Smart Device support is fantastic and very fast to create.
> Gives you a great graphical control over DLLs, registry entries on device,
> etc.
> Of course, it costs about $1100 and Windows Installer technology comes with
> VS.Net 2003, so you have to factor that in.
>
> One more point - VS 2005 (Whidbey) has a new project type called a
> Smart Device Deployment project. I've tried this out and while it's a lot
> nicer
> than the current "Build CAB" capability in VS2003, it is not as intuitive
> and
> flexible as InstallShield.
>
> -Darren
>
>
> "charliewest" <charliewest@discussions.microsoft.com> wrote in message
> news:E2386798-52B3-4D8B-9531-E2F6EB0E4204@microsoft.com...
> > Thanks Darren. This is what i am looking for. I am lost however, regardig
> > how
> > Windows Installer or InstallShield interact w/ ActiveSync? Is this process
> > managed automatically by either of these tools, or does special code need
> > to
> > be written to work w/ activesync?
> >
> > "Darren Shaffer" wrote:
> >
> >> Charlie,
> >>
> >> Your options are:
> >>
> >> 1. treat CAB files as the unit of deployment, which can be moved to
> >> device
> >> through
> >> a web or cradle connection (you'll need separate CABs for each device
> >> family). Encapsulate
> >> everything in you need to deploy into one or more CAB files.
> >>
> >> 2. build a Windows Installer package and distribute this package on CD.
> >> this can
> >> accommodate all device families in a single installer disc.
> >>
> >> 3. use a tool like Installshield 9.x and above, which has excellent
> >> support
> >> for
> >> Smart Device installer projects, and distribute on CD. this can also
> >> accommodate all device families in a single installer disc.
> >>
> >> As far as your idea to deploy on flash disks, this is effective for
> >> things
> >> that can
> >> run from memory cards (which is most things), but not everything (SQL CE
> >> for
> >> example)
> >> works well on a memory card.
> >>
> >> Hope this is what you were looking for.
> >>
> >> -Darren
> >>
> >> "charliewest" <charliewest@discussions.microsoft.com> wrote in message
> >> news:50441168-7C41-451D-B957-BE80A017D844@microsoft.com...
> >> >I need to distribute a CAB files, dependency files and Sql Server Ce
> >> >via:
> >> > - Media (Flash disks or CD)
> >> > - Website
> >> >
> >> > What is the apppropriate package format and deploymment tool for each
> >> > requirement? I am developing with VS.NET 2003 Prof Ed and have seen
> >> > several
> >> > types of setup and deployment projects.
> >> >
> >> > Thanks.
> >>
> >>
> >>
>
>
>