* First try at refactor of Prepare.targets
* Enable restore of CLI build tasks
* Fix up build
* Feedback
* Newlines
* Add new props to sln
* CommitCount
* NuGet.config
* WorkingDir
* packages dir path
* Add missing nuget.configs
* Workaround for https://github.com/NuGet/Home/issues/4583
* Match NuGet.Config casing
* Put back Version Badge Properties
* Remove duplicate
* Bump MSBuild Version to 15.1.0-preview-000503-01
* tool_csc->tool_roslyn
* pull some properties up to dir.props
* Move Roslyn to "Roslyn" subdirectory
* Fix relative paths in RunCsc.*
* Add removal of csc & vbc from deps.json
* Revert roslyn to 2.0.0-rc3-61212-03
* netcoreapp -> 1.0.3
Works around NuGet parallel restore timeouts becoming build failures when the machine has a slow connection, for example in our Docker Fedora containers.
* Eliminate CleanPublishOutput
* Decompose Crossgen Task
* WiP
* TarGzFileExtractToDirectory
* FixModeFlags --> CHMod
Also various eliminations of dead code
* Tasks cleanup
Move all tasks to .tasks file. There is little value in keepint them in each source file as they are already being used assumptively by files that happen to get executed later.
Also eliminating uses of <Exec> for DotNet invocations
* Move to BuildTools implementation of TarGzCreateFromDirectory
* Eliminate Command.cs and helpers
* Remove dead code
* Revert TarGz from BuildTools
Latest build tools package has not picked up the task, though it is checked in.
* Disable ChMod on Windows
* Windows bug fix
* PR Feedback
* Finish changing Chmod caps
* Rebase
* Remove Multi-Project Validator
* Remove projectmodelserver tests
* Enable test package creation
* Incremental test restore
* WiP
* Enable Test Asset Project restore
* Build Test Assets & Restore Test Projects
* Build Test projects
* Enable Test Execution
also moves Test Targets to a well-known CLI Version [Stage 2]
* Pass throuh existing telemetry profile
* 2-space tabs
* Revert TestTargets.cs
* WiP PR feedback
* Refactoring
* Fix naming of RestoreTestAssetPackages
* DotNetTest task
* Fix merge issue
* ExecuteWithCapturedOutput
MSBuild considers StdErr output to be failures. This causes output of any test command which is expected to produce an error to be swallowed in the test.
* Workaround for always-on tracing functionality in dotnet-test
* Fix Path Separator Windows/Unix
* Seperate package build from pack
* Windows Pathing issues
* PR Feedback
* Workaround for msbuild #773https://github.com/Microsoft/msbuild/issues/773
CompileTargets moved to MSBuild. Still need to work on input/outputs, refactoring of targets, specially around CompileStage and moving some of the tasks back to msbuild instead of C# code.