DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

+ Reply to Thread
Results 1 to 4 of 4
  1. 01-01-2002 08:58 PM #1
    PhilipL Guest

    App.Version Question


    I developed a program that will have an option to check if there is a newer
    version available by comparing the current app version to the version numbers
    I store in a db table. My question is should i combine the major,minor and
    version into one number or use each number separately separated by a period
    (1.0.1 or 101) to compare the two. If someone has another idea on doing this
    please let me know?

    Thanks in advance.
    Reply With Quote Reply With Quote
  2. 01-01-2002 09:51 PM #2
    PhilpL Guest

    Re: App.Version Question


    "John V. Barone" <baronej_2000@yahoo.com> wrote:
    >
    >
    >For ease of comparison, I would definately go with a number (as opposed
    =
    >to a string). Numbers are easier to do direct comparisons with; with =
    >strings you have to be careful of the leading "0"s, which can lay waste
    =
    >even the best laid plans...
    >
    >Couple thoughts:
    >1. If you know that you won't have minor or revision #s greater than 9
    =
    >(or 10 if you count "0" as okay to use), you can try something like:=20
    >app.Major + (app.Minor /10) + (app.Revision /100)
    >to generate your app #s.
    >
    >2. Personally, I've been messing more with the idea of using the year =
    >as the project major # and the day of the year as the minor #. You can
    =
    >get the day of year easily by running the following in the immediate =
    >window:
    >datepart("y", now)
    >
    >You can then generate a number by=20
    >app.Major + (app.Minor /1000) + (app.Revision / 10000) 'this will allow
    =
    >you 10 revisions per day!
    >
    >For instance, a number with today as the base would be: 2002.001 =
    >(assuming a revision # of 0)
    >
    >I'm starting to like this approach because I can tell at a glance when a
    =
    >particular version was completed (as opposed to trying to figure out =
    >when version 1.2.3 was/is active)...
    >
    >HTH,
    >John Barone
    >
    >
    >"PhilipL" <aplatfl@aol.com> wrote in message =
    >news:3c326945$1@147.208.176.211...
    >>=20
    >> I developed a program that will have an option to check if there is a
    =
    >newer
    >> version available by comparing the current app version to the version
    =
    >numbers
    >> I store in a db table. My question is should i combine the major,minor
    =
    >and
    >> version into one number or use each number separately separated by a =
    >period
    >> (1.0.1 or 101) to compare the two. If someone has another idea on =
    >doing this
    >> please let me know?=20
    >>=20
    >> Thanks in advance.
    >
    >
    ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    ><HTML><HEAD>
    ><META http-equiv=3DContent-Type content=3D"text/html; =
    >charset=3Diso-8859-1">
    ><META content=3D"MSHTML 5.50.4912.300" name=3DGENERATOR>
    ><STYLE></STYLE>
    ></HEAD>
    ><BODY>
    ><DIV><FONT face=3DArial size=3D2>For ease of comparison, I would =
    >definately go with=20
    >a number (as opposed to a string).* Numbers are easier to do direct =
    >
    >comparisons with; with strings you have to be careful of the leading =
    >"0"s, which=20
    >can lay waste even the best laid plans...</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2>Couple thoughts:</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2>1.* If you know that you won't =
    >have minor or=20
    >revision #s greater than 9 (or 10 if you count "0" as okay to use), you
    =
    >can try=20
    >something like: </FONT></DIV>
    ><DIV><FONT face=3D"Courier New" size=3D2>app.Major + (app.Minor /10) + =
    >(app.Revision=20
    >/100)</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2>to generate your app #s.</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2>2.* Personally, I've been messing =
    >more with=20
    >the idea of using the year as the project major # and the day*of =
    >the=20
    >year*as the minor #.* You can get the day of year easily by =
    >running=20
    >the following in the immediate window:</FONT></DIV>
    ><DIV><FONT face=3D"Courier New" size=3D2>datepart("y", now)</FONT></DIV>
    ><DIV><FONT face=3D"Courier New" size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2>You can then generate a number by =
    ></FONT></DIV>
    ><DIV><FONT face=3D"Courier New" size=3D2>app.Major + (app.Minor /1000) +
    =
    >
    >(app.Revision / 10000)* 'this will allow you 10 revisions per=20
    >day!</FONT></DIV>
    ><DIV><FONT face=3D"Courier New" size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3D"Courier New" size=3D2>For instance, a number with =
    >today as the=20
    >base would be: 2002.001* (assuming a revision # of 0)</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2>I'm starting to like this approach =
    >because I can=20
    >tell at a glance when a particular version was completed (as opposed to
    =
    >trying=20
    >to figure out when version 1.2.3 was/is active)...</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2>HTH,</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2>John Barone</FONT></DIV>
    ><DIV><FONT face=3DArial size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2></FONT>*</DIV>
    ><DIV><FONT face=3DArial size=3D2>"PhilipL" <</FONT><A=20
    >href=3D"mailto:aplatfl@aol.com"><FONT face=3DArial=20
    >size=3D2>aplatfl@aol.com</FONT></A><FONT face=3DArial size=3D2>> =
    >wrote in message=20
    ></FONT><A href=3D"news:3c326945$1@147.208.176.211"><FONT face=3DArial=20
    >size=3D2>news:3c326945$1@147.208.176.211</FONT></A><FONT face=3DArial=20
    >size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> <BR>> I =
    >developed a=20
    >program that will have an option to check if there is a newer<BR>> =
    >version=20
    >available by comparing the current app version to the version =
    >numbers<BR>> I=20
    >store in a db table. My question is should i combine the major,minor =
    >and<BR>>=20
    >version into one number or use each number separately separated by a=20
    >period<BR>> (1.0.1 or 101) to compare the two. If someone has another =
    >idea on=20
    >doing this<BR>> please let me know? <BR>> <BR>> Thanks in=20
    >advance.</FONT></BODY></HTML>


    Is there a way to change the major/minor/revision numbers through code or
    can this only be done manually?

    PhlilpL

    Reply With Quote Reply With Quote
  3. 01-01-2002 10:41 PM #3
    John V. Barone Guest

    Re: App.Version Question

    For ease of comparison, I would definately go with a number (as opposed to a string). Numbers are easier to do direct comparisons with; with strings you have to be careful of the leading "0"s, which can lay waste even the best laid plans...

    Couple thoughts:
    1. If you know that you won't have minor or revision #s greater than 9 (or 10 if you count "0" as okay to use), you can try something like:
    app.Major + (app.Minor /10) + (app.Revision /100)
    to generate your app #s.

    2. Personally, I've been messing more with the idea of using the year as the project major # and the day of the year as the minor #. You can get the day of year easily by running the following in the immediate window:
    datepart("y", now)

    You can then generate a number by
    app.Major + (app.Minor /1000) + (app.Revision / 10000) 'this will allow you 10 revisions per day!

    For instance, a number with today as the base would be: 2002.001 (assuming a revision # of 0)

    I'm starting to like this approach because I can tell at a glance when a particular version was completed (as opposed to trying to figure out when version 1.2.3 was/is active)...

    HTH,
    John Barone


    "PhilipL" <aplatfl@aol.com> wrote in message news:3c326945$1@147.208.176.211...
    >
    > I developed a program that will have an option to check if there is a newer
    > version available by comparing the current app version to the version numbers
    > I store in a db table. My question is should i combine the major,minor and
    > version into one number or use each number separately separated by a period
    > (1.0.1 or 101) to compare the two. If someone has another idea on doing this
    > please let me know?
    >
    > Thanks in advance.

    Reply With Quote Reply With Quote
  4. 01-01-2002 11:36 PM #4
    John V. Barone Guest

    Re: App.Version Question

    I believe it can only be done manually.

    John Barone

    "PhilpL" <aplatfl@aol.com> wrote in message
    news:3c3275bf$1@147.208.176.211...
    >
    > "John V. Barone" <baronej_2000@yahoo.com> wrote:
    > >
    > >
    > >For ease of comparison, I would definately go with a number (as opposed
    > =
    > >to a string). Numbers are easier to do direct comparisons with; with =
    > >strings you have to be careful of the leading "0"s, which can lay waste
    > =
    > >even the best laid plans...
    > >
    > >Couple thoughts:
    > >1. If you know that you won't have minor or revision #s greater than 9
    > =
    > >(or 10 if you count "0" as okay to use), you can try something like:=20
    > >app.Major + (app.Minor /10) + (app.Revision /100)
    > >to generate your app #s.
    > >
    > >2. Personally, I've been messing more with the idea of using the year =
    > >as the project major # and the day of the year as the minor #. You can
    > =
    > >get the day of year easily by running the following in the immediate =
    > >window:
    > >datepart("y", now)
    > >
    > >You can then generate a number by=20
    > >app.Major + (app.Minor /1000) + (app.Revision / 10000) 'this will allow
    > =
    > >you 10 revisions per day!
    > >
    > >For instance, a number with today as the base would be: 2002.001 =
    > >(assuming a revision # of 0)
    > >
    > >I'm starting to like this approach because I can tell at a glance when a
    > =
    > >particular version was completed (as opposed to trying to figure out =
    > >when version 1.2.3 was/is active)...
    > >
    > >HTH,
    > >John Barone
    > >
    > >
    > >"PhilipL" <aplatfl@aol.com> wrote in message =
    > >news:3c326945$1@147.208.176.211...
    > >>=20
    > >> I developed a program that will have an option to check if there is a
    > =
    > >newer
    > >> version available by comparing the current app version to the version
    > =
    > >numbers
    > >> I store in a db table. My question is should i combine the major,minor
    > =
    > >and
    > >> version into one number or use each number separately separated by a =
    > >period
    > >> (1.0.1 or 101) to compare the two. If someone has another idea on =
    > >doing this
    > >> please let me know?=20
    > >>=20
    > >> Thanks in advance.
    > >
    > >
    > ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    > ><HTML><HEAD>
    > ><META http-equiv=3DContent-Type content=3D"text/html; =
    > >charset=3Diso-8859-1">
    > ><META content=3D"MSHTML 5.50.4912.300" name=3DGENERATOR>
    > ><STYLE></STYLE>
    > ></HEAD>
    > ><BODY>
    > ><DIV><FONT face=3DArial size=3D2>For ease of comparison, I would =
    > >definately go with=20
    > >a number (as opposed to a string). Numbers are easier to do direct =
    > >
    > >comparisons with; with strings you have to be careful of the leading =
    > >"0"s, which=20
    > >can lay waste even the best laid plans...</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2>Couple thoughts:</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2>1. If you know that you won't =
    > >have minor or=20
    > >revision #s greater than 9 (or 10 if you count "0" as okay to use), you
    > =
    > >can try=20
    > >something like: </FONT></DIV>
    > ><DIV><FONT face=3D"Courier New" size=3D2>app.Major + (app.Minor /10) + =
    > >(app.Revision=20
    > >/100)</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2>to generate your app #s.</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2>2. Personally, I've been messing =
    > >more with=20
    > >the idea of using the year as the project major # and the day of =
    > >the=20
    > >year as the minor #. You can get the day of year easily by =
    > >running=20
    > >the following in the immediate window:</FONT></DIV>
    > ><DIV><FONT face=3D"Courier New" size=3D2>datepart("y", now)</FONT></DIV>
    > ><DIV><FONT face=3D"Courier New" size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2>You can then generate a number by =
    > ></FONT></DIV>
    > ><DIV><FONT face=3D"Courier New" size=3D2>app.Major + (app.Minor /1000) +
    > =
    > >
    > >(app.Revision / 10000) 'this will allow you 10 revisions per=20
    > >day!</FONT></DIV>
    > ><DIV><FONT face=3D"Courier New" size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3D"Courier New" size=3D2>For instance, a number with =
    > >today as the=20
    > >base would be: 2002.001 (assuming a revision # of 0)</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2>I'm starting to like this approach =
    > >because I can=20
    > >tell at a glance when a particular version was completed (as opposed to
    > =
    > >trying=20
    > >to figure out when version 1.2.3 was/is active)...</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2>HTH,</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2>John Barone</FONT></DIV>
    > ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
    > ><DIV><FONT face=3DArial size=3D2>"PhilipL" <</FONT><A=20
    > >href=3D"mailto:aplatfl@aol.com"><FONT face=3DArial=20
    > >size=3D2>aplatfl@aol.com</FONT></A><FONT face=3DArial size=3D2>> =
    > >wrote in message=20
    > ></FONT><A href=3D"news:3c326945$1@147.208.176.211"><FONT face=3DArial=20
    > >size=3D2>news:3c326945$1@147.208.176.211</FONT></A><FONT face=3DArial=20
    > >size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>> <BR>> I =
    > >developed a=20
    > >program that will have an option to check if there is a newer<BR>> =
    > >version=20
    > >available by comparing the current app version to the version =
    > >numbers<BR>> I=20
    > >store in a db table. My question is should i combine the major,minor =
    > >and<BR>>=20
    > >version into one number or use each number separately separated by a=20
    > >period<BR>> (1.0.1 or 101) to compare the two. If someone has another =
    > >idea on=20
    > >doing this<BR>> please let me know? <BR>> <BR>> Thanks in=20
    > >advance.</FONT></BODY></HTML>
    >
    >
    > Is there a way to change the major/minor/revision numbers through code or
    > can this only be done manually?
    >
    > PhlilpL
    >


    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Forum Rules
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


Top DevX Stories

Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL


Sponsored Links