When running our determinism tests we need to copy the diagnostic file from the intermediate directory
<!--
When running our determinism tests we need to copy the diagnostic file from the intermediate directory
to the location of the binary. This ensures .dll and .dll.key are next to each other to be picked up
by our test scripts
-->
...
...
@@ -414,7 +414,7 @@
</PropertyGroup>
</Target>
<!-- The path to IBCMerge.exe must be specified at build time via $(IbcMergePath). Typically this is passed as a
<!-- The path to IBCMerge.exe must be specified at build time via $(IbcMergePath). Typically this is passed as a
build definition variable -->
<Target Name="ApplyOptimizations"
Condition="'$(OfficialBuild)' == 'true' AND '$(NonShipping)' != 'true' AND '$(SkipApplyOptimizations)' != 'true' AND Exists('$(OptimizationDataFile)') AND Exists('$(IbcMergePath)')"
...
...
@@ -430,16 +430,16 @@
</Target>
<!-- This is part of our developer convenience work to allow easy testing of our portable
unit test projects. It's a similar mechanism to CopyNuGetImplementations but is
<!-- This is part of our developer convenience work to allow easy testing of our portable
unit test projects. It's a similar mechanism to CopyNuGetImplementations but is
both unsupported and somewhat special cased to our build setup.
This bug tracks getting an official solution out of MSBuild.
This bug tracks getting an official solution out of MSBuild.
<!-- Workaround until we move to Microsoft.Net.Compilers.nupkg with this fix: https://github.com/dotnet/roslyn/commit/05c12ebfcdd08a02dbceded5327a8da7a7df23be:
Use the Microsoft.Net.Compilers.props file with the fix checked into the repo instead of the one that comes along with the nuget package:
Use the Microsoft.Net.Compilers.props file with the fix checked into the repo instead of the one that comes along with the nuget package:
<ErrorCondition="$(BuildNumber.Split('.').Length) != 2">BuildNumber should have two parts (in the form of 'x.y')</Error>
<!-- Split the build parts out from the BuildNumber which is given to us by MicroBuild in the format of yyyymmdd.nn
where BuildNumberFiveDigitDateStamp is ymmdd (such as 60615) and BuildNumberBuildOfTheDay is nn (which represents the nth build
where BuildNumberFiveDigitDateStamp is ymmdd (such as 60615) and BuildNumberBuildOfTheDay is nn (which represents the nth build
started that day). So the first build of the day, 20160615.1, will produce something similar to BuildNumberFiveDigitDateStamp: 60615,
BuildNumberBuildOfTheDayPadded: 01; and the 12th build of the day, 20160615.12, will produce BuildNumberFiveDigitDateStamp: 60615, BuildNumberBuildOfTheDay: 12 -->
<!-- Additionally, in order ensure the value fits in the 16-bit PE header fields, we will only take the last five digits of the BuildNumber, so
...
...
@@ -50,7 +50,7 @@
<NuGetPackageRootCondition="'$(NuGetPackageRoot)' == '' and '$(OS)' != 'Windows_NT'">$(HOME)\.nuget\packages</NuGetPackageRoot>
