News for hackers. Stuff that matters.
Re:Introducing STFU: Command line C# projects by eropple on Friday May 27, 2011 @11:01AM (#2591677)
"Actually", it doesn't make it really simple to do that at all. This is considerably more complex than copying a 'build all in directory' build file in and running msbuild on it. (Such a build file is the moral equivalent of the generic makefile that most C/C++ programmers have in their back pocket.)

And even tiny bits of code often need to be able to things that are rather basic within the framework. Importing System.* assemblies, for example.

Still smells like a solution looking for a problem.

Re:Introducing STFU: Command line C# projects by Cymen on Friday May 27, 2011 @11:10AM (#2591702)
I just tried it and it was simple enough to use. After using it though I agree -- I'd prefer my own rolled batch file as it has conventions built in that aren't to my taste.

By importing System.* assemblies do you mean automatically adding some boiler plate "using System.*"?

Re:Introducing STFU: Command line C# projects by eropple on Friday May 27, 2011 @11:25AM (#2591760)
I meant making assembly references. I tried it with System.Drawing and csc complained about not being able to find it.

System.dll isn't enough to really stand up anything that isn't very trivial.