folkslinux
/
windows-terminal
mirror of https://github.com/microsoft/terminal.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
windows-terminal/custom.props

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

12 lines
549 B
Plaintext
Raw Normal View History

consolidate PackageES versioning in /custom.props (#3672) This location and name is practically mandated by PackageES. Sorry ☹️. This will ensure that all artifacts that we produce are versioned properly: | thing | version (ex.) | |---------|-----------------| | dll/exe | 0.7.1911.22009 | | nupkg | 0.7.191122009 | | appx | 0.7.3269.0 | For reference, here's the version format: ### EXE, DLL, .NET Assembly 0.7.1911.22009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### NuGet Package 0.7.191122009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### AppX Package 0.7.03269.0 ^ ^ ^ ^^ ^ | | | || `-Contractually always zero (a waste) | | | |`-Build # on that date | | | `-Number of days in [base year] | | `-Number of years since [base year] | `-Minor `-Major [base year] = $(XesBaseYearForStoreVersion) It is expected that the base year is changed every time the version number is changed.
2019-11-26 03:29:40 +08:00
<?xml version="1.0" encoding="utf-8"?>
Make ToolsVersion more consistent in our project files (#13535) While working on another PR related to this I noticed that my VS generates `.vcxproj` files that are a bit different to the ones we have. This commit is a quick search & replace of all our project files to make (primarily) their `ToolsVersion` more in line with what VS does itself: No `ToolsVersion` for `.vcxproj`, `ToolsVersion="15.0"` for `.csproj` and `ToolsVersion="4.0"` for `.filters` files.
2022-07-27 06:31:42 +08:00
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
consolidate PackageES versioning in /custom.props (#3672) This location and name is practically mandated by PackageES. Sorry ☹️. This will ensure that all artifacts that we produce are versioned properly: | thing | version (ex.) | |---------|-----------------| | dll/exe | 0.7.1911.22009 | | nupkg | 0.7.191122009 | | appx | 0.7.3269.0 | For reference, here's the version format: ### EXE, DLL, .NET Assembly 0.7.1911.22009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### NuGet Package 0.7.191122009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### AppX Package 0.7.03269.0 ^ ^ ^ ^^ ^ | | | || `-Contractually always zero (a waste) | | | |`-Build # on that date | | | `-Number of days in [base year] | | `-Number of years since [base year] | `-Minor `-Major [base year] = $(XesBaseYearForStoreVersion) It is expected that the base year is changed every time the version number is changed.
2019-11-26 03:29:40 +08:00
<!-- This file is read by XES, which we use in our Release builds. -->
<PropertyGroup Label="Version">
<XesUseOneStoreVersioning>true</XesUseOneStoreVersioning>
version: bump to 1.18 on main
2023-01-21 05:24:02 +08:00
<XesBaseYearForStoreVersion>2023</XesBaseYearForStoreVersion>
version: bump to 1.1 on master
2020-05-05 09:52:44 +08:00
<VersionMajor>1</VersionMajor>
version: bump to 1.19 on main Signed-off-by: Dustin Howett <duhowett@microsoft.com>
2023-05-12 05:33:47 +08:00
<VersionMinor>19</VersionMinor>
consolidate PackageES versioning in /custom.props (#3672) This location and name is practically mandated by PackageES. Sorry ☹️. This will ensure that all artifacts that we produce are versioned properly: | thing | version (ex.) | |---------|-----------------| | dll/exe | 0.7.1911.22009 | | nupkg | 0.7.191122009 | | appx | 0.7.3269.0 | For reference, here's the version format: ### EXE, DLL, .NET Assembly 0.7.1911.22009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### NuGet Package 0.7.191122009 ^ ^ ^ ^ ^ ^ | | | | | `-Build # on that date | | | | `-Day | | | `-Month | | `-Year | `-Minor `-Major ### AppX Package 0.7.03269.0 ^ ^ ^ ^^ ^ | | | || `-Contractually always zero (a waste) | | | |`-Build # on that date | | | `-Number of days in [base year] | | `-Number of years since [base year] | `-Minor `-Major [base year] = $(XesBaseYearForStoreVersion) It is expected that the base year is changed every time the version number is changed.
2019-11-26 03:29:40 +08:00
<VersionInfoProductName>Windows Terminal</VersionInfoProductName>
</PropertyGroup>
</Project>