Geek Answers Handbook

In SemVer, why should there be builds + versions of files when releasing beta to the public?

Let's say we release the .net library for the first time. We want to go through the Beta + Release Candidate phase in order to get feedback from early users.

So, in the context of SemVer, we originally released a version 1.0.0-Beta1. With the increase in beta and the release of candidates after that.

As an argument, we can say that our current version number 0.3.0

So, from SemVer we need to get what needs to be placed in different .net records. Those who:

1. Nuget Version

Used to designate a nuget package, and also used by nuget to sort the package and receive if it is a pre-release.

2. Build Version

Remember that assemblies can be strong, and link forwarding can make it difficult to switch between bets when changing an assembly version

3. Version of the build file

What the "File Version" displays in the file properties dialog

4. Information version of the assembly

What the "Product Version" displays in the file properties dialog

+4
source share
1 answer

, SemVer 4 , , . , (, , ..). , 4 .

, NuGet SemVer NuGet, AssemblyInfo Task.

, , , .

+1

More articles:


All Articles