[tree_of_item]

Quick question for .NET developers: is there a solution for totally command line driven workflows yet? I really don't want to mess around with .SLN files and IDEs like Visual Studio and MonoDevelop. I'm sure VS is fine for people who like it, but I really want something like `cargo build` or `go build`.

[muttech]

.NET CORE is exactly this (https://github.com/dotnet/cli)

'dotnet build' to build it.

[AlexC04]

yes and no of course ... yes dotnet cli will be exactly this and it will be GREAT (IMO)

but it isn't actually "out" yet (you can get your hands on it but it will be buggy)

still, will be 100% fantastic.

[swalsh]

I've been using it on a production project. Life hasn't been smooth, but once Its totally functional.

[ZenoArrow]

Look into the tooling around F#, you can use most/all of it using the command line and simple text editors. Much of it can be applied to C# too. FAKE is a good place to start:

http://fsharp.github.io/FAKE/

Forge is also worth checking out:

https://github.com/fsprojects/Forge/blob/master/README.md

One more suggestion, if you'd like an easy (but simple) all-in-one solution for F#, check out Ionide:

http://ionide.io/

[sago]

`mcs` to compile code, rough equivalent of javac

`mono` to run it, rough equivalent of java.

We code for the Unity game engine, but use command line mono tools for testing and feature development.

[ColinDabritz]

On the editing experience side, OmniSharp brings a richer text-editing experience to dot net development on many existing platforms and editors, including command line classics like emacs and vim.

http://www.omnisharp.net/

[ygra]

A trivial MSBuild project that simply compiles all C# files in the current folder is not hard to write by hand, although taking one generated by VS and trimming it down might be easier. In any case, there is csc as the command-line compiler as well.