What does InstallShieldExpress do that VS.NET does not?

[Tom Couvret]

I've been looking around for installers, as have a lot of people.

Someone on this group suggested trying InstallShield as a way of getting
the CF, SQLCE and MyApp all packaged together.

Well I've installed the eval version of InstallShield, and yes it fits
very nicely into the VS IDE, and lets me build my CAB files, and also
creates a directory structure with one copy of the SQLCE.CAb file and
one of the CF.CAb file for each processor type.

But I already had all that with VS anyway. The thing I was looking for
is the desktop installer that my customers (joe public) could download
and run on their desktop, which would work out everything that was
needed on my PPC and install it. There is no way Joe Public can be
expected to work out what sort of processor they have, and how to
install a cab file, regardless of the instructions I give. Nor of course
should they have to. Most have no idea what the CF or SQLCE even is, and
will just make my app look far too complicated if I start talking about
them.

ezSetup does a very nice job of this for myAPP, but of course cant
install the CF and SQLCE as well if its needed.

Am I missing something with InstallShield? Anyone got better ideas? I'm
going to check out e-pocketsetup as suggested by someone else, anyone
confirm that will do what I am after?

Tom

 

[Y. Sivaram]

Tom,

I am not sure whether it is appropriate to discuss InstallShield issues in
this news group. But as I also had the same issue I will give some details

1) If you choose the Smart Device Project type, it will create only CAB
files that needs to be installed from the device it self, which I do not
think will work for you.

2) Choose a normal project and in the merge module section tick on the WINCE
Object type it will briing up a wizard where it will take you through the
stpes of selcting your cab files including CF, SQLCE etc.

3) Once it is done, now if you build the project you will get a setup.exe
(or MSI file) depending on what you need that can be sent to the client who
can run from their desktop computer.

Best Regards,
Y. Sivaram

 

[Tom Couvret]

Yes I agree this is probably not the best place... but as it pertains to
installing CF apps to the PPC, it probably sneaks in. As far as I can
see the install / deploy process seems to be the biggest hole in the
whole deal.

I have tried to create a normal InstallShield Express project, and I
cant see anywhere in the process where it wants merge modules. It all
seems tailored for a desktop install. Unfortunately when I try and Add
project Output, VS crashes on me which doesnt help much - perhaps the
part I am looking for is after there

I have also put something together using NSIS installer, which looks
hopeful. At least I can get it to do the (possibly) 3 installs. It is up
to the person doing the install to click on the checkbox for SQLCE and
NETCF though, which is not the best option.

You may also confirm for me something I read somewhere else - that if I
am doing an app for the PocketPC, that I can pretty well ignore
everything but ARM processor types. Any comment on that?

Thanks for your interest in this anyway,
Tom.

 

[Y. Sivaram]

Hi Tom,

Sorry for the delay and hope it is not late.

1) Start->Programs->Install Shield->Express 5.0
2) File->New->Express Project
3) Select the Installation Designer Tab
4) In (2) Specify Application data select Redistributables
5) From the list tick Windows CE
6) Follow the wizard
7) Set any other parameter as desired for your set-up
8) Build the project

Please let me know if you need any other details regarding the above.

Regarding PPC, even I think (and distribute) only ARM (Pocket PC 2002 and
earlier) and ARMV4 (Pocket PC 2003) for the PPC devices.

Best Regards,
Y. Sivaram

 

[Tom Couvret]

Hey, thanks again. This worked fine. The whole process really is pretty
slick with this tool - you can see where they are spending your license
dollars!

My only complaint now with this product is the size of the setup file -
if I include the CF and SQLCE for just the ARM processor, I still get an
8mb install. Which looks a little on the hefty side. My NSIS installer
version is a little under 2mb.

Presumably I can cut things out of the InstallShield install, but I
doubt if I'll get it down to anywhere near the size.

Thanks on the advice on the processor too. I've seen other posts that
say ARM only, but I must admit that I have been wondering if those were
old posts pre PocketPC2003, and whether we had to worry about the armv4
as well.

Tom