Drop util assembly

The util assembly was originally intended to be portable between different runners, providing some useful functions. In practice, this has not worked out. Based on my work on the GUI, I've concluded that it's best if e each runner, including third-party runners, provide its own code and only use the bare-bones interface that is provided by the engine.

All of the classes and methods from nunit.util are now part of the nunit-console assembly, whose namespaces have been restructured to keep things neat.

In addition, this pull request does a few other things... TestEventHandler and ColorConsole were dependent on ConsoleOptions, in each case for a single setting. They now simply take that setting.

The copy of the framework lib used by nunit-console for its own tests has been updated. It would be better if we could figure out some other way to keep this up to date, without putting the binary into the repository.
It's not, but there are similar options with multiple values that are, so
this one ended up following the same pattern. Knowledge of the values is
shared only by the options class and the TestEventHandler.

An enum would be nicer, but would take more code if we want to give good
error messages. In fact, I did a spike with an enum and it seemed like too
much trouble.

Charlie


On Mon, Aug 25, 2014 at 5:32 PM, Rob Prouse <notifications@github.com>
wrote:

> In src/nunit-console/TestEventHandler.cs:
>
> >
> > -        public TestEventHandler( ConsoleOptions options, TextWriter outWriter, TextWriter errorWriter )
> > +        public TestEventHandler(TextWriter outWriter, string displayLabels)
>
> Is displayLabels an external Engine interfaces? Is that why it is a string
> and not an enum?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/nunit/nunit-console/pull/41/files#r16689582>.
>