 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Compact Framework / July 2006Application Upgrade Issue with Window Mobile 5.0
With operating system 2003SE or earlier, when the application upgraded itself, The OS does not prompt the user to uninstall the older version of application while upgrade.Hence the required files in the cab are extracted, the older ones are maintained and the application runs successfully. With operating system Window Mobile 5.0, it first uninstalls the older version and then extractes the updater cabs. Only the newly deployed files remain. The user is stuck, the he neither has the older version and the newer one doesnt work since some files are missing now. Do I need to re-deploy all the files again ? Or is there a way to override the default behaviour of Mobile 5 to prompt the user to uninstalls the older version first while upgrade? No, you can not. There's no notion of upgrade on Windows CE at all, each CAB should include everything. If you want to save settings, you can do so using custom setup DLL.  SignatureBest regards, Ilya This posting is provided "AS IS" with no warranties, and confers no rights. *** Want to find answers instantly? Here's how... *** 1. Go to http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactfra mework?hl=en 2. Type your question in the text box near "Search this group" button. 3. Hit "Search this group" button. 4. Read answer(s). > With operating system 2003SE or earlier, when the application upgraded > itself, The OS does not prompt the user to uninstall the older version [quoted text clipped - 13 lines] > older > version first while upgrade? With 2003SE or earlier the method we used worked fine. We used to just bundle the newly added files in the updater cab, download the cab in the same location as the application and exploded the cab. Now when we try it with Window Mobile 5.0 this approach doesnt work. The updater cab otherwise would become too heavy to be downloaded if I would be required to bundle all the files, even if they havent been changed :( Any solutions would be of great help... Thanks, Amruta > No, you can not. There's no notion of upgrade on Windows CE at all, each CAB > should include everything. [quoted text clipped - 18 lines] > > older > > version first while upgrade? Yes, it was a bug/incorrect behavior in WCELOAD, now it's fixed and your "upgrade" hack no longer works. Again, WCELOAD does not have notion of upgrade. If that's what you need you would have to implement it yourself using custom code in setup DLL. I would suggest changing application name in a CAB so these two CABs would install at the same time, e.g. "Application" and "Update to Application". Now setup DLL can detect presence of original application and move files as needed. SignatureBest regards, Ilya This posting is provided "AS IS" with no warranties, and confers no rights. *** Want to find answers instantly? Here's how... *** 1. Go to http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactfra mework?hl=en 2. Type your question in the text box near "Search this group" button. 3. Hit "Search this group" button. 4. Read answer(s). > With 2003SE or earlier the method we used worked fine. > [quoted text clipped - 39 lines] >> > older >> > version first while upgrade? Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.