 |
| ||||
LinqConnect Express is a powerful application developed closely to the Microsoft LINQ to SQL technology, and supporting SQL Server, Oracle, MySQL, PostgreSQL, and SQLite. LinqConnect Express was created to provide a powerful model designer with complete integration to Visual Studio.
LINQ stands for Language-Integrated Query, which means that data retrieval is no longer a separate language. The LINQ engine allows .NET applications to connect to databases without bothering much about columns and rows. The data you receive is automatically formed as objects ready to use by your business logic.
LINQ to Relational Data may be thought of as an object-relational mapping (ORM) tool. The type-safe LINQ queries get compiled into MSIL on the fly, and the query clauses are translated into SQL and sent to the SQL server for execution. The program is designed to make your data access layer as safer and faster as possible.
Here are some key features of "LinqConnect Express":
· Visual schema modelling
· Model-First approach support
· Database-First approach support
· Predefined templates
· dbMonitor support
· SQL Server support
· Oracle support
· MySQL support
· PostgreSQL support
· SQLite support
· Project size limit
· Free for use
Requirements:
· NET Framework 3.5
· Microsoft Visual Studio
Limitations:
· Does not allow customization of code templates
· Limited to 10 entities in the project
What's New in This Release: [ read full changelog ]
· Visual Studio 2012 is supported
· The bug with getting entities from the cache by keys of type Int16 is fixed
· The bug with getting entities directly from the cache for the command First (predicate) etc, is fixed
· The bug with wrong parameters when loading dependent entities with two-level LoadOptions are set is fixed
· The bug with invalid type of parameters used for update commands is fixed (SQLite)
Entity Developer:
· The 'Entity Base' class property, which allows specifying the ancestor class/interface for a particular entity type, is implemen ted
· The behaviour is changed: only particular (not all) property characteristics are regenerated when using Update Model From Database wizard after the metadata of the corresponding column have been changed
· The behaviour is changed: when preserving schema name is disabled, schema name is no more saved for Oracle package functions/procedures
Via: LinqConnect Express 4.1.82
