Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Autoincrement revision number ?

49 views
Skip to first unread message

Patrice Scribe

unread,
Jan 28, 2003, 6:04:25 AM1/28/03
to
Is it possible to auto increment the revision number like in VB6 ?

TIA


Nick

unread,
Jan 28, 2003, 6:14:03 AM1/28/03
to
> Is it possible to auto increment the revision number like in VB6 ?

I think that it does this automatically. I say this as I am developing
something that has quite a long version number now even though I haven't
changed it manually. I prefered the project properties in VB6.

Nick.


Taiwo Ayedun

unread,
Jan 28, 2003, 7:22:42 AM1/28/03
to

You can do this via the AssemblyVersion attribute. See AssemblyInfo.vb in
your .NET project.

Note the following in the file:

' Version information for an assembly consists of the following four values:
'
' Major Version
' Minor Version
' Build Number
' Revision
'
' You can specify all the values or you can default the Build and Revision
Numbers
' by using the '*' as shown below:
<Assembly: AssemblyVersion("1.0.*")>

---
Taiwo

"Nick" <spamyo...@kissmyrim.com> wrote in message
news:u71FR5rxCHA.1288@TK2MSFTNGP11...

Patrice Scribe

unread,
Jan 28, 2003, 9:25:43 AM1/28/03
to
When doing this it seems to me the default number never changes (ASP.NET,
assemblyinfo.vb checked out). From where are taken the default numbers ?

Does it change for your ?

Patrice

"Taiwo Ayedun" <tai...@hotmail.com> a écrit dans le message de news:
elE0tfsxCHA.2604@TK2MSFTNGP12...

Chris Dunaway

unread,
Jan 28, 2003, 9:37:53 AM1/28/03
to
"Taiwo Ayedun" <tai...@hotmail.com> wrote in
news:elE0tfsxCHA.2604@TK2MSFTNGP12:

>
> You can do this via the AssemblyVersion attribute. See AssemblyInfo.vb
> in your .NET project.
>

> ' You can specify all the values or you can default the Build and
> Revision Numbers
> ' by using the '*' as shown below:
> <Assembly: AssemblyVersion("1.0.*")>
>
>

Jeffrey Richter, in his book, "Applied Microsoft .Net Framework
Programming", warns not to use the "1.0.*" syntax. He recommends that the
build number be specifically set to a value. In regards to the automatic
increment of the build number he states:

<QUOTE>
This feature is a bug and shouldn't be used because changing the assembly
version number will break any assemblies that reference this assembly. The
AssemblyInfo.cs file that Visual Studio .Net automatically creates for you
when you create a new project is in error: it sets the AssemblyVersion
attribute so that its major and minor parts are 1.0 and that the build and
revision parts are automatically updated by the compiler. You should
definitely modify this file and hard-code all four parts of the assembly
version number.
</QUOTE>

His book talks about versioning information in detail.

Chris


--
If you don't like lunchmeat, please remove it from my e-mail address to
send me an e-mail

0 new messages