Live data from Hacker News

MSBuild is now open source on GitHub

blogs.msdn.com

81–90 of 185 posts

Re: MSBuild is now open source on GitHub

#83

Earlier quoted context omitted.

So, a troll/idiot tried to be funny. Let's not reward him with any more attention?

I thought it was funny, why are people so touchy about it?

PR are not the place for jokes. Developers have enough to do managing their projects, they don't need to waste time sorting through jokes.

You might say, "it's just one joke, what's the big deal?" One joke, attracts others. Everyone thinks they're funny and their joke with worth everyone else's time to read it. If PR become a place that's acceptable to make jokes, it'll be flooded with noise.

Re: MSBuild is now open source on GitHub

#84

Will this help CMake's ability to generate solution files?

Solution files are easy. Project files (I think you meant project files) are not too hard, if all you want to do is build. Integration with Visual Studio is part of the equation, too.

From memory CMake was only producing VS 2010 project files which then had to be fiddled a bit to upgrade them to 2012 - so a version bump would be appreciated.

Re: MSBuild is now open source on GitHub

#85

Earlier quoted context omitted.

Exactly. Rob was just being an annoying prick.

Jees, what is your issue seriously? It's all just a bit of fun; there is no need to get directly insulting over it.

You absolutely were being an annoying prick. The best thing you can do is own up to it and apologize. Definitely not what you're doing right now, what with the whole "jees, what is your issue" thing.

Re: MSBuild is now open source on GitHub

#86

Earlier quoted context omitted.

Correct, VS commandline calls MSBuild. They're using MSBuild, they just don't know it.

Correct, VS commandline calls MSBuild. That seems like an inaccurate description of what's happening: http://stackoverflow.com/questions/11932164/what-parameters-... They're using MSBuild, they just don't know it. Given the age of projects I've worked on, and that it's unclear whether MSBuild is involved in VS's C++ compilation, I don't think your assumption is correct.

Visual Studio changed to using MSBuild for C++ at the time when the project file extension changed from "vcproj" to "vcxproj".

The change was explicitly to make it so that a C++ project file was an MSBuild script.

Visual Studio absolutely uses MSBuild for C++ projects.

Re: MSBuild is now open source on GitHub

#87
post #21

Earlier quoted context omitted.

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

I got loads of time for that, but I've also suffered at the hands of MSBuild as have thousands of others so the PR seemed like a funny troll at the time. Seriously - I remember at one client there was a specific machine set up to edit the build on because it was the only one that could open the workflow editor without crashing. Why there was a workflow editor to edit MSBuild stuff I don't know but that's that world i…

Workflow editor sounds like Team Build, which is not the same thing.

Re: MSBuild is now open source on GitHub

#88
post #64

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. 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.

What's wrong with MSBuild/XBuild? I just type "msbuild" (or press F5 in VS) and I get result .exe file in 0.2 second. On Linux I type "xbuild" and it's the same. You can use Visual Studio without even knowing msbuild exists. Just occasionally a pre-build or post-build script needs to be added. Makefiles, Gradle or CMake are much slower and very complicated.

MSBuild is a nightmare to debug if you end up writing even moderately complex MSBuild project files. It doesn't help that VS has a completely different implementation of MSBuild which is subtly incompatible with the command-line MSBuild.

Also, setting up proper dependency tracking, so that builds are incremental, is considered an "advanced topic", and is extremely difficult to get right in the presence of various kinds of generated files in the build. In these cases, it is much, much slower than a modern build tool like ninja.

MSBuild being open source is going to save countless hours of building workarounds for bugs that have been acknowledged and gone unfixed, or debugging strange problems.

I'm happy to see that it's happened, but would have been much happier had it happened a year ago and saved me months of build system hell.

Re: MSBuild is now open source on GitHub

#90
post #3

Sort of off topic, but I've always wondered if github charges larger orgs for hosting their projects like this. It seems like google and and microsoft get tons of free bandwidth from github to the point of being unsustainable w/o charging.

I know both MS and Google have contracts with GH and are paying 6 figure sums annually, but I'd better keep my source confidential.

Can't you just give your confidential source the MIT license?
Post reply on HN