AssemblyVersion

[GoogleCodeExporter]

It doesn't seem like you are planning to use the AssemblyVersion attribute in 
the Properties\AssemblyInfo.cs.

I'd like to suggest that you enter something like

[assembly: AssemblyVersion("2010.06.28.0")]
[assembly: AssemblyFileVersion( "2010.06.28.0" )]

to help developers trace the assembly back to a specific version.

The attached image shows the assembly file version with (right) and without 
(left) the changed versioning information.

Original issue reported on code.google.com by robin.th...@gmail.com on 11 Jul 2010 at 10:12

Attachments:

• ProductVersionExample.png

[GoogleCodeExporter]

Good idea; added in revision 70

Original comment by lidg...@gmail.com on 13 Jul 2010 at 2:33

• Changed state: Fixed

[GoogleCodeExporter]

Of course with this versioning scheme in place you would want to update the 
version when releasing. Perhaps some kind of script to update it when you 
package a new version would do the trick.

Keep up the good work!

Original comment by robin.th...@gmail.com on 11 Mar 2011 at 7:04

[GoogleCodeExporter]

Yeah; very easy to forget; something automatic would be good. Also; this 
requires a file to be checked in for every release.
Still; it's the best thing available I think. Just added a new download with 
version updated.

Original comment by lidg...@gmail.com on 11 Mar 2011 at 11:16

[GoogleCodeExporter]

I agree with you, I have forgotten the version number many times and it is also 
somewhat unnecessary to list the version change in the SVN log, but still it is 
a change to the code and by that logic it has the rights to be logged.

Thanks for making the change.

Original comment by robin.th...@gmail.com on 12 Mar 2011 at 9:43