Problem

Currently the ScriptCS.NUnit repo will crash under the default roslyn engine. The roslyn in-memory engine (or mono) works fine. However, I cannot specify which engine to run the script against. As a workaround I can use the debug flag, but that produces overly verbose output compared to the normal.

Proposal

A

Add a command line argument Engine which will take a named engine. This will add flexibility as to how ScriptCS executes the scripts and create a way to test scripts against different engines.

B

Implement a command line argument Verbose which will display verbose output. This will preserve existing functionality, but will be a breaking change.

I have the ability to take this issue (or pair) if it is adopted.