Assembly version Why the same?

[Cocotteseb]

Hello all!

Here is my problem: I have a project since several months started and
updated. I get the number of the assembly (which is 1.0.*) and the
build is 2260.
I created a new project since one weelk (to simplify). I put assembly
version as 0.2.* but the build number returns me 2260 exactly the same
as my first 'old' app. It is unbelievable that the build number for my
second app is right.
Assemblys versions aren't different for each project? VS.NET doesn't
have any option to put an incremental build number version different
for each projects?
Thanks!

 

[Daniel Moth]

Show how you retrieve that version number

Cheers
Daniel

 

[Cocotteseb]

Simply like this :version =
System.Reflection.Assembly.GetExecutingAssembly.GetName.Version.ToString
and put it in a label.
For the build version it
is:System.Reflection.Assembly.GetExecutingAssembly.GetName.Version.Build.ToString

 

[Daniel Moth]

Just to keep things simple, I am assuming this code is called in the exe
itself, right? (i.e. not from a dll)

You said the build is 2260. If you had said 2268 I'd start guessing you
somehow get the framework's build number (RTM) back but clearly not the
case...

So can you try a different target? If you are doing this in emulator, try it
on device and the vice-versa. Before that, check in file explorer on the
desktop that the version number really is what you think it should be.

Also what language, IDE and NETCF version are you using?

Cheers
Daniel

 

[Cocotteseb]

It is from the exe himself indeed.
For the build in my 'old' project I deeply think it is normal because I
see it evoluating because of changes, etc. from build 2250...So If it
was the framework build number I would not see any changes.
It returns me the same result on the emulator and on my device
(WM2003SE)
It also return me the 'correct' build number : it the same as I can see
in the file explorer even if the number of build is strange.
I have the impression that my two projects share the same version
number.... It is really strange.
Both to vb.NET, VS2005 (one upgraded from vs 2003) and CF 1.0
Cheers

 

[Daniel Moth]

Can you post an example project? You must be having the
AssemblyVersionAttribute point to a fixed version somehow...

Cheers
Daniel