George,
Everything works well. Apparently the installer 'cab' file was not created in
the folder from which I began the application but the installer.exe was. That
is what I will send to customers. However, how would the installer be created
if a device is not available? Windows mobile device
If ActiveSync/WMDC does not see the device, you do have to use the CAB
file. The exe file is made at the same time the CAB file is made. But
I'm not sure you're using the right file.
Your cab file should be something like myProject.Installer.cab, while
the installer will be named
Oh, THAT property window, duh! I told you I was dense. Ok, George, you answered
my questions. By the way, I didn't include the real name created by the
installer because it was so long but it did create it. I now have also selected
'retain the cab' file.
My assumption is that if you don't
George,
Disregard my last paragraph. I just noticed that regardless of a device being
connected, the project.installer.exe and project.installer.cab files are
still created. I would have sworn that nothing happened before when I pressed
'Start'...only an empty black dos screen.
--- In
To make it clear for others who might read the thread: With NS Basic/CE
8.0, you no longer need to distribute a runtime. It's all built in.
My assumption is that if you don't have a device with which to create
the installer, and only use an emulator, you will still have to send a
separate runtime
