I hope you don&#x27;t mind me replying here.  I figure if you&#x27;re working on the tools you might appreciate some feedback...<p>Annoyingly it seems to work differently to how DNX builds.  With my project [1] I have spent what felt like an age setting up a .NET Core supported project.json that builds with &#x27;dnx build&#x27;;  the result is horror slow compilation and maxed out CPU usage whenever I build in VS2015, even if nothing has changed - actually borderline unusable.  I have rebuilt all of the csproj files and the sln that I originally deleted to make way for the project.json and xproj files.  So I now have:<p><pre><code>  * project.json per folder
  * &lt;project name&gt;.project.json per folder
  * &lt;project name&gt;.csproj per folder
  * &lt;project name&gt;.xproj per folder
  * &lt;project name&gt;.sln per folder
</code></pre>
The per xproj sln is tedious just so I can tick a box saying &#x27;Produce output&#x27;, like I&#x27;d ever <i>not</i> want to produce output.  Total mess.<p>So I thought I&#x27;d give this (dotnet CLI) a go.  I can&#x27;t run from the root because there&#x27;s not a project.json there.  If I go into the Core project then it compiles OK (on OSX with no issues), but builds in the &lt;project&gt;&#x2F;bin folder like MSBuild.  That means the other projects in the repo can&#x27;t find their references like they can with the DNX artifact system.  It seems to me that it should support the same DNX project.json&#x2F;global.json dependency system.<p>Whilst I support the general direction MS is taking with DNX and &#x27;dotnet&#x27;.  The whole system is a buggy inconsistent mess and has recently lost me weeks of time trying to figure out the magic combination of settings that are needed to support cross-platform builds (actually most of the time has been spent waiting for builds, waiting for VS2015 to stop locking up, or giving VS2015 enough &#x27;lock up time&#x27; before killing it from the Task Manager and starting again).<p>I&#x27;m also not sure MS has quite prepared itself for the public evolution of their tools and source.  It has lead to a trail of misinformation throughout the web - and I for one have found the process incredibly difficult to follow.  Trying to piece together what is going-on through github issues on the aspnet&#x2F;dnx&#x2F;fsprojects repos is tedious.  I still don&#x27;t really know if I&#x27;m doing it right and the &#x27;official&#x27; help is light on details at best.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;louthy&#x2F;language-ext" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;louthy&#x2F;language-ext</a>