Release 2.3.0
This relates to PR #16
Strong Naming of Libraries
In this version we now have signed the DLL with our Private Key.
For those that aren't concerned with Strong Named libraries there is no change to the core behaviour; continue using the SDK as you normally would.