github.com/mono/corert.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2018-06-21	Rev netcoreapp2.0 to netcoreapp2.1 (#5974)	Adeel Mujahid

2017-10-03	Fix VS2017 IntelliSense (#4643)	Jan Kotas

2017-09-21	Update ilc to netcoreapp2.0 (#4581)	Jan Kotas

2017-07-07	Remove UnNeeded package build Target (#4102)	Tarek Mahmoud Sayed
	We used this target as a hack till we update the build tools to v2.x and now we updated the build tools so this target is not needed anymore
2017-06-29	Delete stale lines from dir.targets (#4013)	Michal Strehovský
	I was looking at diagnostic logs trying to decypher why I'm getting warnings about some loose *.dll files I have at the root of my drive that has CoreRT repo, but got distracted by seeing attempts to resolve things in the /Documentation directory. This is a set of some old workarounds that used to be in the CoreFX repo too, but are no longer there. Maybe we don't need them anymore?
2017-06-27	Fix rough edges after CLI update (#3983)	Jan Kotas
	* Move build-restore.cmd back to build-managed buildpipeline needs to be updated to make this split * Cleanup dir.props/dir.targets * Add back VS clues * Reformat whitespaces to match VS convention
2017-06-24	Update CoreRT build to use latest .NET CLI and build tools (#3916)	Jan Kotas
	- 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
2017-06-17	Delete ToolsVersion attribute from msbuild files	Jan Kotas
	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]
2017-05-11	Update the packaging license link to MIT (#3580)	Tarek Mahmoud Sayed
	* Update the packaging license link to MIT * Update the Url to point at the same repo
2017-02-25	Update build tools to latest (#2815)	Jan Kotas
	* Update BuildToolsVersion to latest * Cleanup CLSCompliant warnings * Delete workaround that is no longer needed * Download .NET Core 1.1 * Fix Roslyn props * MSBuild.exe was renamed to MSBuild.dll * Fix CoreCLR tests * Rename netcoreapp12 -> netcoreapp20 * Fix UnitTests runs * Fix RemoveEmptyFinalizers CodeAnalysis warnings * Port init-tools.sh cleanup from CoreCLR
2016-10-01	Redirect git rev-parse HEAD error output (#1967)	Jan Kotas
	Redirect git rev-parse HEAD error output to avoid bogus messages about missing git tool when building inside VS and not having git on the path.
2016-04-18	Switch to standardized init-tools scripts	Jan Kotas
	- 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
2015-12-02	Switch to dotnet tools and add unix testing	Senthil
	- Fix few issues and produce xunit format - Set HOME if undefined and DOTNET_HOME - Enable CPP and JIT for all platforms except OSX o CLI has no support for RyuJIT.
2015-09-30	Add initial corert build scripts	dotnet-bot
	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.