Fixed - IndexService.IndexEntity not returning Success result

Tidied up code ready for release. Updated to latest nunit package.

Fixed bug in EntityDeleteTask - term was not specified.

Started code documentation

Removed dependency on DirectoryInfo (abstracted into IIndexLocation)
Added "attributes" object dictionary to IndexOptions (for storing additional index information)
Removed IIndexWriter IEquatable as no longer required

Minor changes. Added IIndexWriter property to IIndexService (necessary for storing any type of IIndexService)
Added extension method for locating a valid IIndexService in a list.

Merged in changes from Comparable branch

Added support for changing analyzers in the IIndexWriter
TODO:We'll need to add something to the QueryBase that will allow us to use analyzers/queryparsers.

Experimental - IndexService can be resolved by evaluating the equality of IIndexWriter.IndexOptions

Merged in IndexService from Compare branch

RecreateIndex is now set within IndexOptions (available for all IIndexWriter implementations)

Made the IIndexTask expose IIndexWriter rather than an index location

Made SearchService non generic. Should be able to use the same instance of SearchService for multiple queries (on the same index).

Added a better example of comparing IndexServices when processing the index queue.

Removed IEquatable from IndexService. IIndexWriter is now exposed as a property (removed Lucene IndexWriter property as this was not being used externally)
Comparing index services can now be done by evaluating the equality of their IndexWriter property (see IndexQueueTestFixture for example)

Made recreatedIndex optional on DirectoryIndexWriter

Allowed IndexWriters to be compared.
Also all comparing IndexServices against IndexWriters for ease of development.

Added lucene.net nuget package

Added lucene.net nuget package

Merged in changes from Test branch (does not include PK changes)

Add IIndexWriter to the IIndexTask (for got to do this in last commit).
This sets the way for creating IndexServices from an IIndexTask

Made IIndexTask generic for easy comparing, leaving IIndexTask (non generic) for use is situations where you won't know (or need to know) the generic's type.
Also made IndexTaskBase implement IIndexTask<T> and also made a non generic version (which I don't think people will use).
Also made IIndexTask<T> implement IEquatible<T> because that is what is was meant for, to force people to compare against other objects of the same type.
This serves a couple purposes
1. Provides an abstract base IndexTask that allready implements most of the equals and has an abstracts out everything that is task specific. This will make it so you don't have to implement IIndexTask<T> every time.
2. It removes the equirement to implement Equals for every situation, execpt Equals(T) where T is itself (same type). This is forced through abstract Equals(T).

Added test for the DequeueAll() method

Add method to get all tasks in queue

Added extension methods for working with lucene documents