cli

there is not much windows only, check github status of dotnet/cli (the sdk), https://github.com/dotnet/cli#build-status, lots of os supported, just clone + build

It's a good point, and i think now is fixed. Really few people just call the compiler directly. before there was the msbuild but was ugly from command line: - msbuild /t:Build /p:Configuration=Release That's why the created the .net core sdk (http://github.com/dotnet/cli). it's always the compiler all the way down. but you can do - `dotnet new -t console` for template - `dotnet build -c Release` to compile - `dotnet run` to build+run - `dotnet pack` to build+ create a package - `dotnet publish -r osx` to build+create standalone version - `dotnet test` to build+run tests

To build off of enricosada's post, this is indeed being tracked and actively worked on right now. More information here: https://github.com/dotnet/cli/issues/3705#issuecomment-22889... Known issues will also be updated, as will documentation on how to use F# on .NET Core.

It is annoying. The preview MSIs are signed but the preview PKGs are not. The last release was so maybe it just takes some time? BTW you can ctrl-click/right-click the installer package and select open to get the option to run it without fully disabling gatekeeper. [https://github.com/dotnet/cli/issues/3434]

Clickable link: https://github.com/dotnet/cli/pull/2145 Sorry, I should have made the thread link directly to that issue.

Source: https://github.com/dotnet/cli/pull/2145 Major violations of privacy happening in the .NET Core RC2 release. If you have anything even vaguely sensitive in your build scripts you may be in violation of your company's privacy rules. I expect massive lashback when this gets into the public eye but in the mean time be very careful using .NET Core RC2 in any sensitive projects. Quotes from the first link: "We collect the following pieces of data: * The command being used (e.g. "build", "restore") * Arguments passed to the command * ExitCode of the command * For test projects, the test runner being used * Timestamp of invocation * Details about the project commands are invoked on * Framework used * If RIDs are present in the "runtimes" node * The CLI version being used"

We're working on this issue. See open issues: https://github.com/dotnet/cli/blob/rel/1.0.0/Documentation/k...

.NET CORE is exactly this (https://github.com/dotnet/cli) 'dotnet build' to build it.

They were likely referring to the cross-platform .NET Core stuff: https://github.com/dotnet/cli

This argument is basically argumentum ad populum, and your concluding sentence is nothing more than the very same statement that I originally refuted. > Even as open source .NET is still a huge pain to get running under Linux and development of .NET anything is extremely difficult without Visual Studio (which doesn't run on Linux). Not only that but most of the .NET libraries one would use for any given purpose only work on Windows. So even if the core of .NET is open source and cross platform any software written using that platform can only effectively run on Windows. https://github.com/dotnet/cli The open-sourcing and cross-platform development of .NET is an ongoing process that's still in its infancy. Yes, of course it's a pain in the ass right now. Installing git on Windows was also a pain in the ass, and even now it's still basicall

Looks like they have compiler support for only C# (csc), and F# (fsc) right now. https://github.com/dotnet/cli/tree/master/src/Microsoft.DotN... https://github.com/dotnet/cli/tree/master/src/Microsoft.DotN...