Windows Mobile forum: Windows Install Class in MSI

I'm writing such things in VS2008 and let's just say the installer is from the dark ages of development. Here's what we ended up doing. "Nothing."

Since there was no budget to create a better installer we decided with live with VS2008's Windows Mobile installer.
Bob

Given time, money and more you can do about anything. But let me warn you of another bump in the road (more like a brick wall.) I have 5 Windows Mobile machines at my disposal for testing and development which appear to give me a good representation of "typical" WM machines.

I have WM 2003SE, WM 5.0, WM 6.0, WM 6.1 WM 6.5 and am previewing some WM 7.0 items. On top of that some like the HTC Touch Pro 2 put a skin on top of it all.

My apps are very industrial and cost conscious to a fault. We reached the point where we can install with the .CAB fine but given the minefield of differences across just 5 machines would you support each variant as it came along?

That is where it could get expensive as you collect each machine, each version of WM that it can have and then sort it all out.

Not impossible but would you turn a profit on that?
Bob

PS. Yes, I'm authoring WM Apps. Just not "installers."

The reality is that the stock .CAB installer and the MSDN Windows example installer work without flaw in WM 5.0 and WM 2003SE. Where it begins to fall apart was on the 6.0+ versions.

But here's what you revealed. It appears you don't have the machines to see this so you might question this. Let me write that unless you have the target machines, you might think there are no problems like this.

Here's the ugly truth. You (or the developer) needs the target machines. Or they may fail.

-> Define "work." The simple CAB file installer that runs on the WM machine to install, does install but there are other issues and I take it that you wanted an installer for the Windows side to chat with ActiveSync, etc. Again, a deep definition of "work" would be required. This area is full if potholes, glitches and gotchas. I'm here, I have platforms and made sure our development contracts did not include any installer.
Bob

Not today. Neat idea but it would be costly as you would have to spend the time on spec writing than actual work. Then you can be assured that everyone would ask "why didn't it work?" or other questions.

I know we are asking questions about the Widcomm Bluetooth stack and the answers have been less than helpful.

Anyhow why wouldn't your software team have the target machines? I know that without them I would not know where things are slow, fast or when the OS renders different on this or that platform.

Your install questions are easy to answer and cheap when you have the real thing to work with.

While I have 5 WM machines to work with, acquiring them ran under 1K or about the price of VS 2008. To me it seems to be the price of admission.

What you may want to know is some makers/vendors/cellphonecompanies have "seed" programs. The HTC unit is a seed unit. I have to give it back when they ask.
Bob