GenericDataManager 1.5.5.2

.NET Framework
There is a newer version of this package available.
See the version list below for details. 
dotnet add package GenericDataManager --version 1.5.5.2
NuGet\Install-Package GenericDataManager -Version 1.5.5.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="GenericDataManager" Version="1.5.5.2">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add GenericDataManager --version 1.5.5.2
#r "nuget: GenericDataManager, 1.5.5.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install GenericDataManager as a Cake Addin
#addin nuget:?package=GenericDataManager&version=1.5.5.2

// Install GenericDataManager as a Cake Tool
#tool nuget:?package=GenericDataManager&version=1.5.5.2

A concurrent data manager that gives IUnitOfWork repositories for each of your entities. Each one gives you One, All, Count, Exists, Add, Update, Delete with single record or bulk operations.

Product Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.0.3.3 1,152 7/27/2017
2.0.3.2 967 3/13/2017
2.0.1.1 1,099 11/3/2016
2.0.0.48-beta 787 10/15/2016
2.0.0.5-alpha 959 10/12/2016
1.5.5.2 1,151 10/8/2016
1.5.5.1 1,439 9/30/2016

- Fixed the issue in QuickLock that causesed it to be in locked state at creation sometimes
- Fixed the issue of "cannot start a new transaction" on DbContext when multiple threads are involved
- DataManager correctly keeps track of DbContexts with the threads
- DataManager requires ConnectionParameters struct for initialization rather than multiple parameters
- DataManager throws exception if disposed when the DbContext seem to be in use by other threads
- multiple threads can simaltaneously access database without locking each other in isolated manner (Entities attached to different thread's DbContext cannot be used by other threads unless detached)