DapperRow dynamic invocation fails in Visual basic - fix

Implement connection-string equivalence (similar to https://github.com/SamSaffron/dapper-dot-net/pull/80)

Fix Issue131

@david.obando

Rainbow: Ignore Id property when calling Table.Insert 

Updated Table methods to better support multi-DB

"Id" is being removed most places in Rainbow, but not on Table.Insert. I
changed this to make it consistent with SqlCompactTable.Insert and
Table.Update.

Fixed DapperTable issue

Added database schema support to Dapper.Rainbow

Bug fix for "Invalid attempt to call MetaData when reader is closed"

Added possibility to add custom type maps - enables serialization of enums to DbType.String instead of DbType.Int32

Would occasionally generate exception "Invalid attempt to call MetaData when reader is closed"

Allows a class to have a reserved word as a column name.

This fixes a bug found in CS 51509960 where the following sequence would
result in an InvalidOperationException being thrown due to an attempt to
access a disposed of DataReader:

- Perform a dynamic query that yields no results
- Add data to the source of that query
- Perform a the same query again

Insert failed when a word such as order was used as a column name.
Added [] around the column name.

Also modified the test for InsertGetUpdate().  The first Get is now a
User instead of IUser.  There is some bug where using the interface
twice first on a null result and then on the real result causes the
reader to not be open when trying to map the type.

No sense in escaping TableName only for update, "from" isn't universally
optional for deletes, First() should be virtual to allow alternatives to
TOP 1

Dapper row

Replaced FastExpando with DapperRow/DapperTable. The primary motivation for this is increased performance when creating lot of rows. In addition DapperRow has a smaller memory footprint.

Pull request 55 (thanks: haeal), with some tweaks; better handling of shutting down the data-reader on the happy path

Applied partial to all Dapper classes and interfaces in order to improve extensibility

Multi-Mapping issue with SplitOn

Dapper by source to extend the Dapper classes without making changes to
the Dapper source (for instance in order to expand DynamicParameter with
a method HasValue<T>(string name)). In addition to further help developers
that reference Dapper by source the public property of Dapper classes are
moved to separate partial classes. By default the previous behavior is kept
but when referencing by source you can now make the Dapper classes internal
by defining: DAPPER_MAKE_PRIVATE

There was a small issue when SplinOn spaces between commas, for example:
splitOn: "AddressId, Id".
For more info see:
http://stackoverflow.com/questions/11042618/dapper-multi-mapping-issue

I have modified below line of code:
From: var currentSplit = splits[splitIndex];
To: var currentSplit = splits[splitIndex].Trim();

Also added a test called:
TestMultiMappingWithSplitOnSpaceBetweenCommas()