Question

I’m using a linked AssemblyInfo.cs file to set the AssemblyFileVersion for all of my class libraries.

[assembly: AssemblyFileVersion("6.60.3.4")]

I’m using the local/default AssemblyInfo.cs file for everything else.

//example of AssemblyVersion set in project AssemblyInfo.cs    
[assembly: AssemblyVersion("6.60.3.1")]

My result is that the AssemblyFileVersion and the AssemblyVersion are both getting set to the AssemblyFileVersion value.

How can I maintain a shared AssemblyFileVersion and seperate AssemblyVersions for each of my project assemblies?

EDIT

I was under the impression that I could/should use the AssemblyFileVersion to track the release version for all dll assemblies in my project. The thought would be to have the exe and dlls all have the same AssemblyFileVersion. The AssemblyVersion would only be incremented when modifications occurred to that specific dll. This logic makes sense to me. Please advise if there are more logical approaches to handling large projects

Answer 1

My question was correctly stated, but I’m wondering if I was misled a little. I was using the Windows file properties dialog to confirm that my ProductVersion and FileVersion were getting set properly.

I added the following to my shared AssemblyInfo.cs file and it started working as I expected.

[assembly: AssemblyVersion("6.60.0.0")]    
[assembly: AssemblyInformationalVersion("6.60.0.0")]

Any thoughts why this would update the AssemblyVersion instead of just this

[assembly: AssemblyVersion("6.60.0.0")]