How did you go about this:
- did you use exe and dlls or created a cab file?
- as far as deployment goes, did you implement a web service updater or use a third party deployment tool?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Definitely go with CAB and MSI files. See this great article in MSDN for details. CAB files are created with Visual Studio’s Set Up projects. It is very easy to create a CAB file that contains your exe, dll and configuration files. You can instruct where these files should be copied to. You can also add registry values. Another good feature is that CAB files wont install in an incompatible platform.
With a little bit of more effort you can create a MSI installer. In it you can bundle more than one CAB files, one for every platform you want to support. Since you are not using ActiveSync, this is not much of an option for you.
For updating applications, this is another good article. Although it is old, I think that it still presents some useful ideas.
My recommendation is to use CAB files both for installation and updating the application. There is a relevant question here in SO about how to update an application over the air.