Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MSBuild is going cross-platform with .NET Core

blogs.msdn.com

Post reply on HN
Print view View original

51–60 of 139 posts

Re: MSBuild is going cross-platform with .NET Core

#51

Post by nathanaldensr »

swozey wrote: post #9
BinaryIdiot wrote: post #3

I know MSBuild gets a lot of hate but this is still great news. The end goal of having a .Net project be compile-able on Windows, Linux and Mac is going to be awesome. I'm curious, when everything is finally done, what the adoption rates will be like. Will hard-core Linux users who used Java migrate when it makes sense? Will they avoid it because "M$"? All good stuff.

It will be very nice to be able to do CI/compilation on extremely cheap and fast (to spin up) linux slaves as opposed to requiring an expensive (license, hardware) and slow (miserably slow ec2 boots) Windows servers.

Good Lord, yes. It takes forever for my TeamCity build agent AMIs to spin up and actually connect to the TeamCity server. It would be awesome to replace that bulky Windows build agent with a Linux one.

Re: MSBuild is going cross-platform with .NET Core

#52

Post by wsc981 »

akshayB wrote: post #6

This is good news but little bit too late. Microsoft strategy of sticking with windows to slow down Linux and Mac back fired . If they opened up .Net few years back cross platform app development landscape would have been totally different today.

I'm not sure Microsoft came too late to the party. Perhaps MSBuild is a bit crappy (I don't know, never used it), but I can imagine Roslyn becoming more useful now on other platforms since it's open sourced. It'll be great that one can be sure the runtime behaves the same on all platforms Roslyn will run on. And it'll also be nice if new runtime features will be available on every platform at (more or less) the same time. I think Roslyn could have a nice future ahead. Personally speaking, I find writing C# is much more enjoyable as writing Java.

And who knows, maybe someone will build a decent MSBuild replacement. Or perhaps the Xamarin guys already have a nice alternative.

Re: MSBuild is going cross-platform with .NET Core

#53

Post by wtetzner »

CmonDev wrote: post #32
tomjen3 wrote: post #14

Earlier quoted context omitted.

1 year ago, yes. C# is awesome as a language but I don't see a reason to switch to .net when the JVM has Kotlin, which is nicer than C#, but still super lightweight and thoroughly pragmatic.

Cool! How would you build an app for iOS and WinPhone using Kotlin?

Don't know about Windows Phone, but for iOS you could use RoboVM.

http://robovm.com/

Re: MSBuild is going cross-platform with .NET Core

#54

Post by radicalbyte »

duaneb wrote: post #23
Someone1234 wrote: post #19

Earlier quoted context omitted.

I have no strong opinions for or against MSBuild. What is it that you dislike about it? Or what is it that other tools do that MSBuild fails to do? PS - I have done a lot of .Net development, but rarely did anything beyond the basics with MSBuild directly (mostly via Visual Studio, or took the pre-generated command line and stuck in a script).

> PS - I have done a lot of .Net development, but rarely did anything beyond the basics with MSBuild directly (mostly via Visual Studio, or took the pre-generated command line and stuck in a script). This is an excellent reason to avoid MSBuild. IDE lockin is a nightmare. Might be unavoidable for Visual Studio, though.

It depends what you're doing.

If you're making libraries, console applications or doing modern websites it's pretty easy to get your build working without Visual Studio.

One - ELEPHANT SIZE - problem is that for some reason Microsoft only ship the Windows SDKs as part of Visual Studio. Meaning that you'll need to install the IDE at least once to get a build running (you can copy the SDKs around after that).

Microsofties - I know that a lot of dev-div people will be reading - can you shed some light on this situation? What's the reasoning behind not shipping the SDKs separately. I've never had this problem with Java..

Re: MSBuild is going cross-platform with .NET Core

#57

Post by useerup »

serve_yay wrote: post #26
Someone1234 wrote: post #19

Earlier quoted context omitted.

I have no strong opinions for or against MSBuild. What is it that you dislike about it? Or what is it that other tools do that MSBuild fails to do? PS - I have done a lot of .Net development, but rarely did anything beyond the basics with MSBuild directly (mostly via Visual Studio, or took the pre-generated command line and stuck in a script).

I really hated the language you use to describe build tasks. It is a very frustrating mix of declarative and imperative syntax. And of course, who wouldn't want to write code in XML?! (XML, the markup language, the one we use for marking up information like documents and records.) I was doing fairly complicated tasks with it years ago, and it's just one of those technologies that feels like it is fighting you at ever…

> I really hated the language you use to describe build tasks.

Yup. For some reason that escapes rationality, MS chose to control the build through Workflow Foundation. And they build a horribly complicated WF "script". Pretty much universally hated.

But you may be pleased to know that they have now abandoned that, and each build task can now be described pretty much by the scripting language of your choosing.

Re: MSBuild is going cross-platform with .NET Core

#58

Post by fimoreth »

jongalloway2 wrote: post #47
deegles wrote: post #30

Earlier quoted context omitted.

I read somewhere that Microsoft's structured the patents/licenses in the .NET ecosystem in such a way as to make that kind of lawsuit unlikely. Can anyone comment if that is true?

There are patent pledges and promises not to assert patents: https://msdn.microsoft.com/en-us/openspecifications Portions of .NET are under ECMA and ISO standards: https://en.wikipedia.org/wiki/Common_Language_Infrastructure... I think the most important part is that the new cross-platform .NET core framework, CLR, and compiler (Roslyn) are under permissive open source licenses (MIT for fx and clr, Apache 2 for Rosly…

> 1. Microsoft employee until they notice I'm hanging out on hacker news instead of replying to e-mails and "fix the glitch".

Shh, they might find us.

Re: MSBuild is going cross-platform with .NET Core

#59

Post by Locke1689 »

radicalbyte wrote: post #54
duaneb wrote: post #23

Earlier quoted context omitted.

> PS - I have done a lot of .Net development, but rarely did anything beyond the basics with MSBuild directly (mostly via Visual Studio, or took the pre-generated command line and stuck in a script). This is an excellent reason to avoid MSBuild. IDE lockin is a nightmare. Might be unavoidable for Visual Studio, though.

It depends what you're doing. If you're making libraries, console applications or doing modern websites it's pretty easy to get your build working without Visual Studio. One - ELEPHANT SIZE - problem is that for some reason Microsoft only ship the Windows SDKs as part of Visual Studio. Meaning that you'll need to install the IDE at least once to get a build running (you can copy the SDKs around after that). Microsoft…

Do you mean this[1] Windows SDK?

[1] https://dev.windows.com/en-us/downloads/windows-10-sdk

Re: MSBuild is going cross-platform with .NET Core

#60

Post by romanovcode »

beastway wrote: post #55

Why would I want to deal with MS on any other platform? I want nothing to do with that company out of principal and I hope we can do a equally harmful shut out of MS in the future, they deserve their own medicine. No, into the trash it goes.

>Why would I want to deal with MS on any other platform?

Because C# is a great language.

Post reply on HN