blocks|key|1572016|text|你使用的是什么源码控制系统？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1572017|几乎所有这些文件都有某种形式的$+Id+$标记，当文件签入时，该标记会展开。|1572018|我通常使用某种形式的黑客将其显示为版本号。|1572019|另一种方法是使用日期作为内部版本号:+080803-1448|1572020|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

What source control system are you using? 

Almost all of them have some form of $ Id $ tag that gets expanded when the file is checked in.

I usually use some form of hackery to display this as the version number.

The other alternative is use to use the date as the build number: 080803-1448

blocks|key|1572124|text|VS.NET将程序集版本默认为1.0.*，并在自动递增时使用以下逻辑:它将构建部分设置为自2000年1月1日以来的天数，并将修订部分设置为自本地时间午夜以来的秒数除以2。请参阅此MSDN+article。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1572125|程序集版本位于assemblyinfo.vb或assemblyinfo.cs文件中。从文件中：|1572126|'+Version+information+for+an+assembly+consists+of+the+following+four+values:
'
'++++++Major+Version
'++++++Minor+Version+
'++++++Build+Number
'++++++Revision
'
'+You+can+specify+all+the+values+or+you+can+default+the+Build+and+Revision+Numbers+
'+by+using+the+'*'+as+shown+below:
'+<Assembly:+AssemblyVersion("1.0.*")>+

<Assembly:+AssemblyVersion("1.0.0.0")>+
<Assembly:+AssemblyFileVersion("1.0.0.0")>+|code-block|syntax|javascript|1572127|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.reflection.assemblyversionattribute.assemblyversionattribute.aspx^0|2H|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

VS.NET defaults the Assembly version to 1.0.* and uses the following logic when auto-incrementing: it sets the build part to the number of days since January 1st, 2000, and sets the revision part to the number of seconds since midnight, local time, divided by two. See this <a href="http://msdn.microsoft.com/en-us/library/system.reflection.assemblyversionattribute.assemblyversionattribute.aspx" rel="noreferrer">MSDN article</a>.

Assembly version is located in an assemblyinfo.vb or assemblyinfo.cs file. From the file: 

<pre class="lang-vb prettyprint-override"><code>' Version information for an assembly consists of the following four values:
'
' Major Version
' Minor Version 
' Build Number
' Revision
'
' You can specify all the values or you can default the Build and Revision Numbers 
' by using the '*' as shown below:
' &lt;Assembly: AssemblyVersion("1.0.*")&gt; 

&lt;Assembly: AssemblyVersion("1.0.0.0")&gt; 
&lt;Assembly: AssemblyFileVersion("1.0.0.0")&gt; 
</code></pre>

blocks|key|1572171|text|如果您想要一个在每次编译完成时都会更新的自动递增数字，您可以在预生成事件中使用VersionUpdater。如果您愿意，预构建事件可以检查构建配置，以便版本号只在发布构建时递增(例如)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1572172|entityMap|0|LINK|mutability|MUTABLE|url|http://testdox.wordpress.com/versionupdater/^0|13|E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you want an auto incrementing number that updates each time a compilation is done, you can use <a href="http://testdox.wordpress.com/versionupdater/" rel="nofollow noreferrer">VersionUpdater</a> from a pre-build event. Your pre-build event can check the build configuration if you prefer so that the version number will only increment for a Release build (for example).

blocks|key|1787142|text|我发现只要在需要产品版本的地方使用以下命令就可以很好地显示最后一次构建的日期：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1787143|System.IO.File.GetLastWriteTime(System.Reflection.Assembly.GetExecutingAssembly().Location).ToString("yyyy.MM.dd.HH.mm.ss")|code-block|syntax|javascript|1787144|而不是尝试从以下内容获取版本：|1787145|System.Reflection.Assembly+assembly+=+System.Reflection.Assembly.GetExecutingAssembly();
object[]+attributes+=+assembly.GetCustomAttributes(typeof(System.Reflection.AssemblyFileVersionAttribute),+false);
object+attribute+=+null;

if+(attributes.Length+>+0)
{
++++attribute+=+attributes[0]+as+System.Reflection.AssemblyFileVersionAttribute;
}|1787146|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I have found that it works well to simply display the date of the last build using the following wherever a product version is needed:

<pre><code>System.IO.File.GetLastWriteTime(System.Reflection.Assembly.GetExecutingAssembly().Location).ToString("yyyy.MM.dd.HH.mm.ss")
</code></pre>

Rather than attempting to get the version from something like the following:

<pre><code>System.Reflection.Assembly assembly = System.Reflection.Assembly.GetExecutingAssembly();
object[] attributes = assembly.GetCustomAttributes(typeof(System.Reflection.AssemblyFileVersionAttribute), false);
object attribute = null;

if (attributes.Length &gt; 0)
{
 attribute = attributes[0] as System.Reflection.AssemblyFileVersionAttribute;
}
</code></pre>

blocks|key|1572273|text|这里有一个手动的替代选项:这是我编写的一个快速而又脏的PowerShell片段，它从我们的Jenkins构建系统的预构建步骤中调用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1572274|它将AssemblyVersion和AssemblyFileVersion的最后一个数字设置为BUILD_NUMBER环境变量的值，该值由构建系统自动设置。|offset|length|style|CODE|1572275|if+(Test-Path+env:BUILD_NUMBER)+{
++++Write-Host+"Updating+AssemblyVersion+to+$env:BUILD_NUMBER"

++++#+Get+the+AssemblyInfo.cs
++++$assemblyInfo+=+Get-Content+-Path+.\MyShinyApplication\Properties\AssemblyInfo.cs

++++#+Replace+last+digit+of+AssemblyVersion
++++$assemblyInfo+=+$assemblyInfo+-replace+
++++++++"%5E\[assembly:+AssemblyVersion$`"([0-9]%2B)\.([0-9]%2B)\.([0-9]%2B)\.[0-9]%2B`"$]",+
++++++++('[assembly:+AssemblyVersion("$1.$2.$3.'+%2B+$env:BUILD_NUMBER+%2B+'")]')
++++Write-Host++($assemblyInfo+-match+'%5E\[assembly:+AssemblyVersion')
++++++++
++++#+Replace+last+digit+of+AssemblyFileVersion
++++$assemblyInfo+=+$assemblyInfo+-replace+
++++++++"%5E\[assembly:+AssemblyFileVersion$`"([0-9]%2B)\.([0-9]%2B)\.([0-9]%2B)\.[0-9]%2B`"$]",+
++++++++('[assembly:+AssemblyFileVersion("$1.$2.$3.'+%2B+$env:BUILD_NUMBER+%2B+'")]')
++++Write-Host++($assemblyInfo+-match+'%5E\[assembly:+AssemblyFileVersion')
++++++++
++++$assemblyInfo+%7C+Set-Content+-Path+.\MyShinyApplication\Properties\AssemblyInfo.cs+-Encoding+UTF8
}+else+{
++++Write-Warning+"BUILD_NUMBER+is+not+set."
}|code-block|syntax|javascript|1572276|entityMap^0|0|2|F|I|J|1B|C|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|N|$]]

Here is a handcranked alternative option: This is a quick-and-dirty PowerShell snippet I wrote that gets called from a pre-build step on our Jenkins build system.
It sets the last digit of the <code>AssemblyVersion</code> and <code>AssemblyFileVersion</code> to the value of the <code>BUILD_NUMBER</code> environment variable which is automatically set by the build system.
<pre class="lang-powershell prettyprint-override"><code>if (Test-Path env:BUILD_NUMBER) {
 Write-Host &quot;Updating AssemblyVersion to $env:BUILD_NUMBER&quot;

 # Get the AssemblyInfo.cs
 $assemblyInfo = Get-Content -Path .\MyShinyApplication\Properties\AssemblyInfo.cs

 # Replace last digit of AssemblyVersion
 $assemblyInfo = $assemblyInfo -replace 
 &quot;^\[assembly: AssemblyVersion$`&quot;([0-9]+)\.([0-9]+)\.([0-9]+)\.[0-9]+`&quot;$]&quot;, 
 ('[assembly: AssemblyVersion(&quot;$1.$2.$3.' + $env:BUILD_NUMBER + '&quot;)]')
 Write-Host ($assemblyInfo -match '^\[assembly: AssemblyVersion')
 
 # Replace last digit of AssemblyFileVersion
 $assemblyInfo = $assemblyInfo -replace 
 &quot;^\[assembly: AssemblyFileVersion$`&quot;([0-9]+)\.([0-9]+)\.([0-9]+)\.[0-9]+`&quot;$]&quot;, 
 ('[assembly: AssemblyFileVersion(&quot;$1.$2.$3.' + $env:BUILD_NUMBER + '&quot;)]')
 Write-Host ($assemblyInfo -match '^\[assembly: AssemblyFileVersion')
 
 $assemblyInfo | Set-Content -Path .\MyShinyApplication\Properties\AssemblyInfo.cs -Encoding UTF8
} else {
 Write-Warning &quot;BUILD_NUMBER is not set.&quot;
}
</code></pre>

I would like the version property of my application to be incremented for each build but I'm not sure on how to enable this functionality in Visual Studio (2005/2008). I have tried to specify the AssemblyVersion as 1.0.* but it doesn't get me exactly what I want. 

I'm also using a settings file and in earlier attempts when the assembly version changed my settings got reset to the default since the application looked for the settings file in another directory. 

I would like to be able to display a version number in the form of 1.1.38 so when a user finds a problem I can log the version they are using as well as tell them to upgrade if they have an old release.

A short explanation of how the versioning works would also be appreciated. When does the build and revision number get incremented?

Automatically update version number

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我希望我的应用程序的版本属性在每次构建时都会递增，但我不确定如何在Visual Studio (2005/2008)中启用此功能。我曾尝试将AssemblyVersion指定为1.0.*，但它并没有得到我想要的结果。我还使用了一个设置文件，在前面的尝试中，当程序集版本更改时，我的设置被重置为默认值，因为应用程序在另一个...

问自动更新版本号
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问自动更新版本号EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问自动更新版本号
EN