The, uh, first PR: https://github.com/Microsoft/msbuild/pull/1
MSBuild is now open source on GitHub
21–30 of 185 posts
Re: MSBuild is now open source on GitHub
#22Perhaps we can use this to start making headway in the fight to get rid of make, autotools, and cmake? :)
Re: MSBuild is now open source on GitHub
#23The, uh, first PR: https://github.com/Microsoft/msbuild/pull/1
I wish he had a bit more empathy for whatever poor grunt at Microsoft had to slog through the process of open-sourcing it only to get this in thanks
Re: MSBuild is now open source on GitHub
#24Re: MSBuild is now open source on GitHub
#25Earlier quoted context omitted.
> Nobody is seriously going to fork this and create their own port of MSBuild, possibly one of the most mocked and reviled parts of the .NET ecosystem. You're probably right. But it does mean there's one more part of the .NET ecosystem that potentially runs on Linux and OSX, and that's probably the reasoning behind this.
The reasoning is likely that there is now an internal KPI for open sourcing code because it helps MS PR.
Re: MSBuild is now open source on GitHub
#26Re: MSBuild is now open source on GitHub
#27Re: MSBuild is now open source on GitHub
#28However the mono xbuild tool has subtle incompatibilities and holes in functionality as compared to msbuild so for no other reason than having the "same" build tool in mono and .Net I applaud this move.
Re: MSBuild is now open source on GitHub
#29http://stackoverflow.com/questions/707107/library-for-parsin...
Re: MSBuild is now open source on GitHub
#30Nobody is seriously going to fork this and create their own port of MSBuild, possibly one of the most mocked and reviled parts of the .NET ecosystem. I do however congratulate the ground level MS staffers on the effort it likely took to convice the Risk and Legal departments that open sourcing something like this won't make their business fail. That must have been trying.
> Nobody is seriously going to fork this and create their own port of MSBuild, possibly one of the most mocked and reviled parts of the .NET ecosystem. You're probably right. But it does mean there's one more part of the .NET ecosystem that potentially runs on Linux and OSX, and that's probably the reasoning behind this.