- Pick up latest .NET Core 2.0 CLI and buildtools
- Remove all project.json references and convert everything to msbuild projects
- Stick to vanilla .NET CLI project shape as much as possible. Minimize dependencies on buildtools special behaviors
The latest project templates do not have it, and it is only good for generating warnings like the following in the detailed build log:
Project file contains ToolsVersion="4.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="14.0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424.
[tfs-changeset: 1662024]
* Split pipeline build to match CoreFX's model.
- OS-specific legs no longer publish to MyGet, they just upload to Azure.
- New publish leg downloads from Azure and publishes to MyGet.
- Only includes Microsoft.TargetingPack.Private.CoreRT for now, will add ILCompiler
after we sort out what OS-specific packages should be named.
* Addressing code review feedback (PR#2505).
- Switch over to using standardized init-tools script used by other repos
- Update to recent buildtools
- Switch to running msbuild against CoreCLR instead of mono
- Make build scripts to be otherwise more similar to the ones used by other repos
The CoreFX build.cmd we used as the baseline doesn't need to handle
native build and it can afford to just pass it's command line arguments
to msbuild verbatim. We won't have that luxury in CoreRT since we have
native bits on Windows too.
Fix up project.json files to remove the annoying downgrade warning
messages in Visual Studio.
Change framework in project.json to dotnet, since the other one is
apparently ASP.NET specific.
Disable the framework resource handling that makes our projects include
a phantom Common\src\System\SR.cs file.
I'm not fixing everything with this. We are still using a bunch of
*.target files designed to build the framework to build a compiler,
after all. I don't want to remove that support, because eventually we
will also be building pieces of the framework here, but clearly we need
a way to distinguish between "this is a compiler assembly" and "this is
a framework assembly" at some point.
Populating repo with build infrastructure from the corefx project. Scripts are copied verbatim from the corefx repo as of commit 1ee4f60145a851adbacbb16e7b0c65bec3ec0d02.
Only minor changes were done to remove corefx-specific workarounds.
Also integrating the type system into the build.
Jan Kotas
Chris Rummel
Gaurav Khanna
Michal Strehovský
dotnet-bot