By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,555 Members | 1,589 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,555 IT Pros & Developers. It's quick & easy.

Build number not incrementing on compile

P: n/a
In my project's "AssemblyInfo.vb" file, I have set the following for
versioning:
<Assembly: AssemblyVersion("3.0.*")>

Yet every time I rebuild, I get the exact same build number and private
part number: 3.0.1907.20745

What am I doing wrong, here? I read that the build (1907) and private part
(20745) numbers should be set based on the days past a certain date, and
seconds since midnight, respectively.

TIA
--
Michael
Nov 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"Michael Kellogg" <mk******@WEDELIVERcc3.com> schrieb:
In my project's "AssemblyInfo.vb" file, I have set the following for
versioning:
<Assembly: AssemblyVersion("3.0.*")>

Yet every time I rebuild, I get the exact same build number and private
part number: 3.0.1907.20745

What am I doing wrong, here? I read that the build (1907) and private
part
(20745) numbers should be set based on the days past a certain date, and
seconds since midnight, respectively.


Structure of version numbers and methods to determine the version number
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=versioning&lang=en>

VB6 style versioning
<URL:http://www.jmedved.com/files.asp?id=20401&language=en>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Nov 21 '05 #2

P: n/a
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote:
http://dotnet.mvps.org/dotnet/faqs/?...ioning&lang=en


Hmm. So it gets incremented at each Visual Studio instantiation. I guess
that makes sense for a big shop, but I'm a one-man show and rebuilding
all the time during beta. I might do big revisions two or three times a
day.

Okay, I'm glad I understand that, now. I thought it was like the old VB6
where it increments upon every compilation.

Here's another link a friend sent me on this:
http://groups-
beta.google.com/group/microsoft.public.windows.file_system/msg/8702261793
ca568d?q=AssemblyVersion+default&hl=en&lr=&ie=UTF-8&oe=UTF-8&rnum=1

Thanks for the help.

--
Michael Kellogg
Nov 21 '05 #3

P: n/a
In Jeffrey Richter's book, "Applied Microsoft .Net Framework
Programming", he states not to use the automatic versioning:

"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.vb 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 it's 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."

Chapter 2 of his book goes into detail about the three version numbers
than an assembly has.

Chris

Nov 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.