<story><title>MSBuild is going cross-platform with .NET Core</title><url>http://blogs.msdn.com/b/dotnet/archive/2015/09/03/msbuild-is-going-cross-platform-with-net-core.aspx</url></story><parent_chain><item><author>CydeWeys</author><text>Are there really that many people building .NET projects on non-Windows systems?  It&amp;#x27;s been my experience that companies that are using .NET are pretty much full Windows everywhere.</text></item><item><author>plorkyeran</author><text>I doubt that anyone would choose it for other stacks, but this means that you don&amp;#x27;t need a separate build system for building your existing .NET project on non-Windows.</text></item><item><author>CydeWeys</author><text>I used to work at a mostly-Microsoft shop and I cannot fathom why anyone would want to deal with MSBuild for other platforms.  There are so many better alternatives.  And as bad as MSBuild is for building .NET stuff, at least it&amp;#x27;s the right tool for that job.  Trying to shoehorn it into some other stack entirely, which you know is just going to cause even more pain?  No.  Just no.</text></item><item><author>cptnbob</author><text>Now I can hate every moment of its existence on more than one platform!&lt;p&gt;Having dealt with it for years, it&amp;#x27;s unadulterated pain and bad performance and nothing else.</text></item></parent_chain><comment><author>Locke1689</author><text>Roslyn needs cross-platform MSBuild to build itself for every platform (without Mono). Same with corefx.&lt;p&gt;So even if you&amp;#x27;re currently using or thinking about using .NET xplat and don&amp;#x27;t have any plans to use MSBuild, this move is necessary for us working on .NET to get xplat builds working.</text></comment>
<story><title>MSBuild is going cross-platform with .NET Core</title><url>http://blogs.msdn.com/b/dotnet/archive/2015/09/03/msbuild-is-going-cross-platform-with-net-core.aspx</url></story><parent_chain><item><author>CydeWeys</author><text>Are there really that many people building .NET projects on non-Windows systems?  It&amp;#x27;s been my experience that companies that are using .NET are pretty much full Windows everywhere.</text></item><item><author>plorkyeran</author><text>I doubt that anyone would choose it for other stacks, but this means that you don&amp;#x27;t need a separate build system for building your existing .NET project on non-Windows.</text></item><item><author>CydeWeys</author><text>I used to work at a mostly-Microsoft shop and I cannot fathom why anyone would want to deal with MSBuild for other platforms.  There are so many better alternatives.  And as bad as MSBuild is for building .NET stuff, at least it&amp;#x27;s the right tool for that job.  Trying to shoehorn it into some other stack entirely, which you know is just going to cause even more pain?  No.  Just no.</text></item><item><author>cptnbob</author><text>Now I can hate every moment of its existence on more than one platform!&lt;p&gt;Having dealt with it for years, it&amp;#x27;s unadulterated pain and bad performance and nothing else.</text></item></parent_chain><comment><author>code_sterling</author><text>I&amp;#x27;ll definitely be.  I live in the nix terminal, and that&amp;#x27;s where the tools work best for web development.  But the current day job is C# apps.  I dream of hacking code legitimately in a nix.</text></comment>