Home/ Questions/Q 510939
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T07:09:54+00:00

At my job, the assembly version of each project in the source control is

  • 0

At my job, the assembly version of each project in the source control is kept to 1.0.0.0. When the build machine make a new daily build, it has a task to update the assembly version but does not check in the updated assemblyinfo.cs. So on our dev machines, the assembly version of the dlls we are compiling are always set to 1.0.0.0.

Is it best practice to keep the assembly version up to date in the source control or are we doing the right thing already?

What are the pros and cons of each possibilities?

Thanks

Related or Duplicate:
Should AssemblyInfo.cs be placed in version control?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Con:

    • you cannot debug or test any code that depends on the correct assembly version (if you have such code)

    By the way, there is an easier way to make sure all of your assembly versions are in sync: define a public const string “VersionMask” in a public class VersionInfo in a top level assembly that is referenced by all other assemblies and put

    [assembly: AssemblyVersion(VersionInfo.VersionMask)]

    in every AssemblyInfo.cs file (provided you ar using C#), for VB.NET it is 

    <Assembly: AssemblyVersion(VersionInfo.VersionMask)>
    • 0