Personally, I've run into a lot of friction using Snippet Compiler.
So, I tend to use LINQPad to test snippets. It's pretty convenient for testing individual lines of code, or most "full" program snippets, as well as evaluating LINQ statements against a database.
It features a really awesome view of results, so that complex types are displayed in an easy-to-read structure.
From their site:
- LINQPad reports the execution time in the status bar, so you won't have to manually create a Stopwatch class for performance testing.
- Want to test a variation of your snippet? Ctrl+Shift+C instantly clones your snippet so you can run another version side-by-side.
- You can return to saved queries in single click, thanks to the My Queries treeview. Some people are using LINQPad as a scripting tool!
The only real snag that run into with LINQPad is in the "full program" mode (where you're defining methods, instead of just calling individual statements) you can't create extension methods, because everything happens inside of a the context of a hidden type (and extension methods can't be defined in a nested type).