Devart dotConnect for SQLite v5.15.1612 Professional
Devart dotConnect for SQLite v5.15.1612 Professional
dotConnect for SQLite is a high-performance ORM enabled data provider for SQLite that builds on ADO.NET technology to present a complete solution for developing SQLite-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and facilitates the development of database applications.
Our ADO.NET SQLite provider supports a wide range of SQLite-specific features, such as user-defined functions, CEROD, SQLiteCrypt, and SEE encryption extensions, support for enabling SQLite extensions with connection string parameters, etc.
Advanced Visual Studio Integration
dotConnect for SQLite provides a vast number of GUI tools that increase your productivity. For example, it includes DataSet tools, such as DataSet Wizard, DataSet Editor, DataSet Manager, provide you an easy way to create and edit typed and untyped DataSets.
SQLite ADO.NET Provider supports advanced Visual Studio integration (DDEX), and provides convenient visual component editors to simplify component tweaking.
Broad Compatibility
dotConnect for SQLite was the first SQLite database provider to support .NET Core and Entity Framework Core, and we work hard to support new platforms and development technologies as soon as they are released.
Visual Studio support: 2008 – 2019
Platforms support:
Full .NET Framework 2.0 – 4.8
.NET Core 1.x, 2.x, and 3.1
Enhanced ORM Support
dotConnect for SQLite offers enhanced ORM support with a bundled visual designer for ORM models - Entity Developer. Our SQLite ADO.NET Provider supports the following ORMs:
Entity Framework v1 - v6
Entity Framework Core 1.x, 2.x, and 3.1
NHibernate
LinqConnect
5.15.1612
LinqConnect (formerly known as LINQ to SQLite)
The insert of the object, the type of which is an unmapped class inherited from a mapped class, is supported
The bug with throwing System.NullReferenceException, when constructing the error saying that unmapped class is not supported, is fixed
Entity Developer
Command-line interface is implemented in a standalone Entity Developer
The new property Context Name is added to Model Properties in EF Core Model
The new property Target Framework is added to Model Properties in EF Core Model
The provider registration is improved: requirement to put provider registration entry in the config file is not obligatory anymore
Create Model Wizard is improved: now it allows installing multiple NuGet packages on the final step
Model file tree in .NET Core / .NET Standard projects is improved: all generated code files and model files are nested under the same node in Solution Explorer
Entity Framework support
Entity Framework Core 3.1.3 is supported
The .ToString() call for numbers, DateTime/DateTimeOffset properties and values in LINQ queries in EF Core is supported
The call of Convert.ToString(value) in LINQ queries in EF Core is supported
The bug with comparing milliseconds of DateTime properties is fixed
LinqConnect (formerly known as LINQ to SQLite)
The insert of the object, the type of which is an unmapped class inherited from a mapped class, is supported
The bug with throwing System.NullReferenceException, when constructing the error saying that unmapped class is not supported, is fixed
Entity Developer
Command-line interface is implemented in a standalone Entity Developer
The new property Context Name is added to Model Properties in EF Core Model
The new property Target Framework is added to Model Properties in EF Core Model
The provider registration is improved: requirement to put provider registration entry in the config file is not obligatory anymore
Create Model Wizard is improved: now it allows installing multiple NuGet packages on the final step
Model file tree in .NET Core / .NET Standard projects is improved: all generated code files and model files are nested under the same node in Solution Explorer
Entity Framework support
Entity Framework Core 3.1.3 is supported
The .ToString() call for numbers, DateTime/DateTimeOffset properties and values in LINQ queries in EF Core is supported
The call of Convert.ToString(value) in LINQ queries in EF Core is supported
The bug with comparing milliseconds of DateTime properties is fixed
Only for V.I.P Warning! You are not allowed to view this text.