From 0241b24b4cb63991972acbb162f7046be4100e7f Mon Sep 17 00:00:00 2001 From: Livar Date: Wed, 3 May 2017 11:14:22 -0700 Subject: [PATCH] Dummy change to force a build. --- Documentation/ProjectJsonToCSProj.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ProjectJsonToCSProj.md b/Documentation/ProjectJsonToCSProj.md index 92a16f4b3..5ad36c7ed 100644 --- a/Documentation/ProjectJsonToCSProj.md +++ b/Documentation/ProjectJsonToCSProj.md @@ -1,4 +1,4 @@ -.NET CLI preview 3 is coming, and with it comes the .csproj project file format and msbuild engine. The team has put a lot of focus on making the transition as seamless as possible, but as with any change of this magnitude there are some gotcha's to keep in mind. This issue explains how to use the .NET CLI during this transitional period. +.NET CLI preview 3 is here, and with it comes the .csproj project file format and msbuild engine. The team has put a lot of focus on making the transition as seamless as possible, but as with any change of this magnitude there are some gotcha's to keep in mind. This issue explains how to use the .NET CLI during this transitional period. # Overview Starting with @coolcsh's great post [Changes to Project.json](https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-to-project-json/) the team has been hard at work moving the .NET command line story from project.json to msbuild. Our plan was fairly straightforward: