Version Control on PocketPC Application

[salimgbelim]

Hi Guys,

Just wondering how other developers manages version control in there
applications?

What i do is everytime i generate a new build i modify the
assemblyinfo.vb's
<Assembly: AssemblyVersion("9.2.2.7")>

and compare it with the server version if it doesn't match i ask client
to download/autoupdate my application.

Any Ideas???? or articles links for controling versions for PPC's?

Regards

Salim

 

[Peter Foot [MVP]]

Have you read this article:-
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/AutoUpdater.asp

Should be very useful.

Peter

 

[salimgbelim]

Hi Peter,

Yes i have already implemented Autoupdater in my application,but my
problem is
my cab file is 4.5MB which downloading over GPRS is not a good idea.

Also by version control i meant is e.g my version number currently is V
9.2.2.9 now i only want to update my application
if Schema is Changed/any parameters changed in webservice webmethod
so in this case how we update the version number do we change to V
9.2.2.10 or do we change to V 9.2.3.0?

Is there any standard procedure to do
1. Version controls on PPC accessing webservice on webserver?
2. How to sync ther version on both Webserver and PPC

Regards
Salim

 

[Steve Maillet \(eMVP\)]

That's a level of version numbering detail that is entirely up to you - it's
pretty arbitrary either way. In general people are used to the idea that
there is a major number a minor number and a build number of some sort. The
build number is updated with ever bug fix or patch. The minor number is
updated with small feature changes or additions, and the major number when
significant changes are made. In other words it comes down to user
expectation of how much "pain" they will go through when migrating/updating
a new version. So long as you convey that information to the customer I
don't think they will care much how you number the versions.