I am guessing not. Or hates it, one or the other.
> The code smells, too. If you don't pass in a command-line argument it's going to barf with an exception. WTF?
(I don't know the author) but in his defense: He started this yesterday and has written about 70 lines of code in 13 commits. Most projects don't really do anything in 70 lines of codes (although there are some notable and AWESOME exceptions.)
msbuild ain't perfect, but at least it can reference the GAC.
This project does not do anything in 70 lines of code. If we wanted we could create this "functionality" with some lines inside a .bat file
I see the name STFU more like instead of having a long (or short) email exchange about how to do something just whip out STFU and do a quick bit of coding to test out your idea.
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.
By importing System.* assemblies do you mean automatically adding some boiler plate "using System.*"?
System.dll isn't enough to really stand up anything that isn't very trivial.
There is also the F# interactive window if you're poking into the BCL while in Visual Studio.
Snippet Compiler isn't broken, though, like STFU is. For instance, I have the .NET framework in C:\WINNT.
Besides, for command line use, how hard is it to:
1. Start menu, Visual Studio Command Prompt 2. vim temp.cs 3. csc temp.exe 4. temp.exe
http://www.sliver.com/dotnet/SnippetCompiler/
I tried it with default parameters and it looks like no go.
this thing seems like a poor solution to a problem that barely exists.
voila, C# REPL! great for testing out code snippets
I do like the idea in practice -- it's simple but useful. It is also short enough that tweaking it to meet my own needs couldn't be simpler. I'll play with it some more.
To be honest, you'd be better off writing that msbuild file mentioned upthread instead of trying to jump on some silly "STFU and code" bandwagon. Unlike this, you can do useful stuff even with a very trivial msbuild file. And you only have to write it once.
And it'll actually work.
The code smells, too. If you don't pass in a command-line argument it's going to barf with an exception. WTF?
Meh--I guess I just don't see the point. If you want to "STFU and code" (what a miserable attempt at a catchphrase), shouldn't you have something that actually works? If I want to "STFU and code" isn't it likely that I might dare to want System.Drawing?
Does the dude not know about msbuild/xbuild or something?