提交 6674df77 编写于 作者: T Tanner Gooding 提交者: GitHub

Merge pull request #15782 from tannergooding/version

Updating the BuildNumber to be 00065535.0 if no BuildNumber was specied.
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) Microsoft. All Rights Reserved. Licensed under the Apache License, Version 2.0. See License.txt in the project root for license information. -->
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!-- This controls the version numbers of the build that we are producing -->
......@@ -22,9 +24,11 @@
<BuildNumber Condition="'$(BuildNumber)' == ''">$(BUILD_BUILDNUMBER)</BuildNumber>
<Error Condition="'$(BuildNumber)' == '' AND '$(OfficialBuild)' == 'true'">A build number must be specified for a signed build.</Error>
<!-- When a build number is not specified, then we should default back to '00000000.0', which is a build number in the
same format as provided by MicroBuild v2, but with all digits set to zero. -->
<BuildNumber Condition="'$(BuildNumber)' == ''">00000000.0</BuildNumber>
<!-- When a build number is not specified, then we should default back to '00065535.0', which is a build number in the
same format as provided by MicroBuild v2, but greater than any that MicroBuild v2 will produce, and is still compatible
with the Win32 file version limitations. This is required so that builds done locally, where '$(OfficialBuild)' == 'true',
can still be deployed to VS and override the version that is globally installed. -->
<BuildNumber Condition="'$(BuildNumber)' == ''">00065535.0</BuildNumber>
<!-- When a build number is specified, it needs to be in the format of 'x.y' -->
<Error Condition="$(BuildNumber.Split('.').Length) != 2">BuildNumber should have two parts (in the form of 'x.y')</Error>
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册