1.2.0

• Production release. No changes from 1.2.0-beta1.

1.2.0-beta1

• The assembly now has a strong name.
• An internal use of JTokenReader is now disposed of after use.
• A null stream passed to the Reader(Stream) constructor will now throw an ArgumentNullException.

1.1.0

• Minor code cleanup.

1.1.0-beta1

• A IOException: Not enough storage is available to process this command
  when using the memory-mapped mode with 32-bit builds or many threads was
  fixed. Closes GH #5.
• Use of streams was replaced with direct access for both the memory-mapped
  file mode and the memory mode. This should increase performance in most
  cases.
• When using memory-mapped mode, the file is now opened with
  FileShare.Delete, allowing other processes to delete or replace the
  database when it is in use. The reader object will continue using the old
  database.
• The Json.NET dependency was updated to 7.0.1.

1.0.1

• Improved the exception thrown when the constructor for Reader is called
  with an empty stream.
• Updated Newtonsoft.Json dependency to 6.0.8.
• Minor code cleanup.

1.0.0

• First production release

0.3.0

• Added public Metadata property on Reader.

0.2.3

• The database is now loadable from a Stream.

0.2.2

• Fixed a bug that occurred when using the memory-mode in a multi-threaded
  application. When using a single Reader from multiple threads in memory-
  mode, the internal state of the object could become corrupt if you replaced
  the MaxMind database file on disk with another database file.

0.2.1

• Fixed bug that caused an exception to be thrown when two threads created a
  MaxMind.Db.Reader object at the same time. This was fixed using a
  synchronization lock around the code that opens/creates the memory map. We
  recommend that you share a Reader object across threads rather than
  create one for each thread or lookup.