[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: C# AssemblyInfo integration

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Wed, 2 Sep 2009 16:12:05 -0500

> -----Original Message-----
> From: si [mailto:sshnug.si_at_gmail.com]
> Sent: Tuesday, September 01, 2009 4:29 AM
> To: Martin Rabl
> Cc: users_at_subversion.tigris.org
> Subject: Re: C# AssemblyInfo integration
>
>
> From what I've read:
>
> .NET version numbers have 4 parts: Major.Minor.Build.Revision
> Windows installer product versions have 3 parts: Major.Minor.Build
>
> See: http://stackoverflow.com/questions/801899/software-versioning-
> difference-in-windows-installer-and-net-version
>
> Inparticular: http://msdn.microsoft.com/en-
> us/library/aa370859(VS.85).aspx
>
> btw, I was wrong about the maximum value, Major and Minor part have
> maximum of 255, Build part has maximum of 65,535.
>

You appear to have other options:
- AssemblyFileVersion doesn't appear to be limited to short ints or even
integers: <Assembly: AssemblyFileVersion("1.13.2559M.0")>
- You can add also add "AssemblyInformationalVersion" which seems to be
string based: : <Assembly:
AssemblyInformationalVersion("svn://server/repos/tags/rel.1.0_at_1234")>
It shows up as "Product Version" in the file properties.

This is on VB 2008 Express.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2390441

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-02 23:14:08 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.