Skip to content

Releases: maxmind/MaxMind-DB-Reader-dotnet

4.3.4

24 Nov 21:33
16f4164

Choose a tag to compare

  • Fourth attempt at Trusted Publishing. No other changes.

4.3.3

24 Nov 21:21
fa4eede

Choose a tag to compare

  • Third attempt at Trusted Publishing. No other changes.

4.3.2

24 Nov 21:11
8ad25f5

Choose a tag to compare

  • Second attempt at Trusted Publishing. No other changes.

4.3.1

24 Nov 21:03
5db62bb

Choose a tag to compare

  • First release via Trusted Publishing. No other changes.

4.3.0

20 Nov 22:03

Choose a tag to compare

  • .NET 10.0 has been added as a target.
  • The language version has been updated to C# 14.0.

4.2.0

05 May 16:27
c1e2b26

Choose a tag to compare

  • .NET 6.0 and .NET 7.0 have been removed as targets as they have both
    reach their end of support from Microsoft. If you are using these versions,
    the .NET Standard 2.1 target should continue working for you.
  • .NET 9.0 has been added as a target.
  • We now use a mutex rather than a lock statement when opening the
    database. This is done to reduce the likelihood of a race condition
    when process are opening a single database when using
    FileAccessMode.MemoryMappedGlobal.
  • Performance improvements. Pull requests by GrAcgoire. GitHub #210, #211
    and #212.

4.1.0

05 Dec 23:31

Choose a tag to compare

  • .NET 5.0 has been removed as a target as it has reach its end of life.
    However, if you are using .NET 5.0, the .NET Standard 2.1 target should
    continue working for you.
  • .NET 7.0 and .NET 8.0 have been added as a target.
  • Minor performance improvements.

4.0.0

03 Feb 22:00
1fa735a

Choose a tag to compare

  • This library no longer targets .NET 4.6.1.
  • .NET 6.0 was added as a target.

3.0.0

16 Nov 23:06

Choose a tag to compare

  • This library now requires .NET Framework 4.6.1 or greater or .NET Standard
    2.0 or greater.
  • .NET 5.0 was added as a target framework.
  • When decoding strings in a memory-mapped file, the reader no longer
    allocates a temporary byte[]. This significantly improves performance but
    requires the use of unsafe code.
  • FileAccessMode.MemoryMapped now works if the database path specified is
    a symbolic link to the actual database.

2.6.1

06 Dec 22:54

Choose a tag to compare

  • netstandard2.1 was added as a target framework.