path: root/Directory.Build.props
AgeCommit message (Collapse)AuthorFilesLines
2019-06-25Tell the compiler to emit nullable attributes for public API only (#25398)Santiago Fernandez Madero1-1/+1
2019-05-21Switch NuGet package build to use Arcade instead of BuildTools (#24619)Elinor Fung1-1/+1
2019-05-06Port all managed product binaries to use SDK style projects (#24285)Aaron Robinson1-1/+4
Convert managed product binary to use SDK project system. - Uses Arcade for versions strings - Overrides Arcade defined output paths - should change in the future
2019-02-20Set copyright and package licenseTomas Matousek1-0/+6
2018-12-14Add Azure DevOps signing support (#21545)Morgan Brown1-0/+1
Add signing support for Azure DevOps pipelines. This uses the arcade signing step, but with custom logic to find files to sign while we're not using arcade for the rest of the build.
2018-07-29Fix invalid IntPtr == null comparisons, set strict mode for Roslyn (#19191)Jacek Blaszczynski1-0/+4
Issue reported in Solution is to compare always against IntPtr.Zero and use Roslyn stric mode for reporting warnings for IntPtr == null comparisons
2017-11-04[Infrastructure] Use MSBuild v15 extension point to control CL parallelism, ↵Jacek Blaszczynski1-0/+5
abstract MSBuild /maxcpucount switch (#14578) This commit frees -ExtraParameters and uses MSBuild v15 extension point to control CL compiler parallelism. If MSBuild 15.0 is available - installed with Visual Studio 2017 - CL parallelism control is achieved by using extension point in Microsoft.Common.props file which allows to include Directory.Build.props - for details see [Microsoft.Common.props] [1] file in MSBuild repo. MSBuild parallelism is controled via abstracted /maxcpucount command line switch which now is available as -MSBuildNodeCount pass through run.cmd/ command line argument with default value equal to /maxcpucount (what defaults to number of logical processors). This allows to control MSBuild parallelism on all supported platforms. It is possible to control MSBuild parallelism programatically via MSBuild public API using MaxNodeCount properties available on the following APIs: Microsoft.Build.Evaluation.ProjectCollection.MaxNodeCount Microsoft.Build.Execution.BuildParameters.MaxNodeCount It's use in current build infrastructure would require creating unnecessary complexity and was ruled out.