Sridhar Periyasamy 8fcfc2af05 Upgrade Corefx and coreclr references ... Microsoft.NetCore.App 1.0.0 => 1.0.1 Microsoft.NETCore.Runtime.CoreCLR 1.0.2 => 1.0.4 CLI Branding "Microsoft .NET Core 1.0.0 - SDK Preview" => "Microsoft .NET Core 1.0.1 - SDK 1.0.0 Preview 2-003122" List of changes - all project.jsons - dotnet new templates - and build projects files - shared-build-targets-utils\DependencyVersions.cs - CliDependencyVersions.cs		2016-08-31 10:41:47 -07:00
..
GivenADotnetFirstTimeUseConfigurer.cs	Introducing a in progress sentinel that gets verified before running the first time experience. If we can get a handle for this sentinel, we proceed with the first time run, otherwise, it means there is a first time experience running already, in which case we continue running dotnet normally, even though the final (real) sentinel is not present yet. This prevents multiple dotnet commands from running the first time experience in parallel and prevents us from running into parallel nuget restores.	2016-06-10 16:54:39 -07:00
GivenANuGetCachePrimer.cs	Adding the code to extract the archive in the first use of dotnet an	2016-06-10 16:54:16 -07:00
GivenANuGetCacheSentinel.cs	Introducing a in progress sentinel that gets verified before running the first time experience. If we can get a handle for this sentinel, we proceed with the first time run, otherwise, it means there is a first time experience running already, in which case we continue running dotnet normally, even though the final (real) sentinel is not present yet. This prevents multiple dotnet commands from running the first time experience in parallel and prevents us from running into parallel nuget restores.	2016-06-10 16:54:39 -07:00
Microsoft.DotNet.Configurer.UnitTests.xproj	Almost all of the code to prime the NuGet cache from the archive.	2016-06-10 16:53:55 -07:00
project.json	Upgrade Corefx and coreclr references	2016-08-31 10:41:47 -07:00