All geek questions in one place

.Net Is it better to check the updated AssemblyInfo.cs assembly in daily assembly?

In my work, the build version of each project in the source control is stored in 1.0.0.0. When the collector creates a new daily assembly, she has the task of updating the version of the assembly, but does not check the updated assemblyinfoinfo.cs. So, on our dev machines, the compiled version of the DLL that we are compiling is always set to 1.0.0.0.

Is it better to use assembly version update in the original control or are we already doing the right thing?

What are the pros and cons of each opportunity?

thank

Associated or duplicate:
Should AssemblyInfo.cs be included in version control?

+3
source share
4 answers

Con:

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

By the way, there is an easier way to make sure that all your versions of the assembly are synchronized: define the public string const " VersionMask" in the public class VersionInfoin the top-level assembly referenced by all other assemblies and put

[assembly: AssemblyVersion(VersionInfo.VersionMask)]

in every AssemblyInfo.cs file (if you use C #), for VB.NET it is

<Assembly: AssemblyVersion(VersionInfo.VersionMask)>
+3
source

, [AssemblyVersion]. , CLR . , GAC. , , , .

[AssemblyFileVersion]. , , . , .

, .NET .NET 2.0 .NET 3.5 SP1. 2.0.0.0, . , , - , , .

+2

, , . , script, assemblyinfo.cs, , .

0

, assemblyinfo.cs, - . Dev env. . .NET-, dll , .

0

Source: https://habr.com/ru/post/1726539/

More articles:


All Articles