Telerik.DataAccess.Core 2014.2.617.2

There is a newer version of this package available.
See the version list below for details.
dotnet add package Telerik.DataAccess.Core --version 2014.2.617.2
NuGet\Install-Package Telerik.DataAccess.Core -Version 2014.2.617.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="Telerik.DataAccess.Core" Version="2014.2.617.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Telerik.DataAccess.Core --version 2014.2.617.2
#r "nuget: Telerik.DataAccess.Core, 2014.2.617.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 Telerik.DataAccess.Core as a Cake Addin
#addin nuget:?package=Telerik.DataAccess.Core&version=2014.2.617.2

// Install Telerik.DataAccess.Core as a Cake Tool
#tool nuget:?package=Telerik.DataAccess.Core&version=2014.2.617.2

The Telerik.DataAccess.Core NuGet package provides the Telerik Data Access runtime assemblies necessary to consume Telerik Data Access persistent objects, without defining any mapping.

If this project contains persistent classes and defines mapping, the Telerik.DataAccess.Fluent NuGet package is required as well.

Telerik Data Access helps defining mapping and executing create, retrieve, update and delete operations for your data access classes and database tables. It allows you to consume stored procedures and functions.

Product Compatible and additional computed target framework versions.
.NET Framework net20 is compatible.  net35 was computed.  net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

GitHub repositories (2)

Showing the top 2 popular GitHub repositories that depend on Telerik.DataAccess.Core:

Repository Stars
aspose-words/Aspose.Words-for-.NET
Aspose.Words for .NET examples, plugins and showcases
KalikoCMS/KalikoCMS.Core
Open source content management system (CMS) for the ASP.NET platform.
Version Downloads Last updated
2015.1.225.1 2,257 2/25/2015
2014.3.1209.1 1,810 12/15/2014
2014.3.1027.1 1,011 10/27/2014
2014.2.918.1 1,576 9/24/2014
2014.2.711.1 1,398 7/21/2014
2014.2.617.2 362 6/18/2014
2014.1.403.2 544 4/9/2014
2014.1.225.3 72 3/12/2014
2014.1.225.2 146 2/26/2014
2013.3.1320.1 166 1/28/2014

New
- Support of ICollection<T>.Contains(T) and Enumerable.Contains<T>(IEnumerable<T>,T) in LINQ projection - ICollection<T>.Contains(T) and Enumerable.Contains<T>(IEnumerable<T>,T) are now supported in the LINQ projection expressions, so that they become usable in group aggregate expressions.

Fixed
- NullReferenceException when second level cache cluster is used in a setup with clients using different meta data and an object with internal identity is evicted - Now the distributed L2 cache is functioning properly when participating servers have similar, but not identical metadata.
- Attempting to read unsigned value stored in some backends resulting in a System.OverflowException - Reading unsigned numeric columns (like ushort) will no longer cause System.OverflowException when loading data from a database supporting unsigned types.
- When calling GetMemberNames() on entity type with internal version column, voa_version member unexpectedly returned - GetMemberNames() method in the OpenAccessContext is no longer returning internal version column (voa_version) for types using ConcurrencyControl.Version.
- OpenAccessContext.GetMemberNames() not returning members defined in base types - OpenAccessContext GetMemberNames() API now returns members defined in base type(s) of the current type.
- Schema Migration: Exception caused by index creation for VARCHAR(MAX) columns - Telerik Data Access will no longer try to automatically create database indexes over data types that cannot be indexed (e.g. varchar(MAX), nvarchar(MAX), blob and etc.) when creating or migrating database schema.


NOTE: These Release Notes include only the runtime changes in the particular Telerik Data Access release. For the full list of changes please refer to the Telerik web site ( http://www.telerik.com/support/whats-new/data-access/release-history ).