How can I make the AssemblyInfo version of a C# .NET CF program propagate to the Explorer Properties window?

Answer 1

Does the AssemblyFileVersion attribute help?

Answer 2

You need to add another attribute:

[assembly: AssemblyFileVersion("1.0.114.0")]

Note that you still need the AssemblyVerison one as well to correctly identify the assembly to the .NET runtime.

Answer 3

The version number does propagate through to the "Version" tab in the properties dialogue but not through to the summary. Unfortunately VS will not auto-populate the summary information of a file as the information is meta-data attached to the file itself. You can however access and manipulate the summary information yourself by using the free DSO OleDocument Properties Reader from Microsoft.

You can acquire the library from: http://www.microsoft.com/downloads/details.aspx?FamilyId=9BA6FAC6-520B-4A0A-878A-53EC8300C4C2&displaylang=en

Further information on its use can be found at: http://www.developerfusion.co.uk/show/5093/

EDIT: As noted above by pb and Nigel Hawkins you can get the property to propogate by using the AssemblyFileVersion attribute like:

[assembly: AssemblyFileVersion("1.0.114.0")]

Answer 4

I'm not sure that RevisionNumber is the correct field to be looking for.

Try explorer, right click -> version tab, and look at the AssemblyVersion field there.

Answer 5

in my project we use FileVersion = YYYY.MM.DD.BUILD (e.g., 2008.9.24.1) but the ProductVersion should be major.minor.revision.BUILD. we use the AssemblyInformationalVersion to get around this.

AssemblyVersion="MAJ.MIN.REV.1" --> used by .NET

AssemblyInformationalVersion="MAJ.MIN.REV.XXX" --> used in explorer's ProductVersion

AssemblyFileVersion="YYYY.MM.DD.XXX" --> used in explorer's FileVersion

Answer 6

Note, that the AssemblyFileVersion attribute is not available under .NET Compact Framework!

See this article from Daniel Mooth for a workaround.