We are glad to annonce the new version of our ADO.NET provider – v1.8.
Main features of new release
1. Added support for .NET Framework v4.7.2.
2. New DDEX providers for Visual Studio 2017:
Full news text: https://www.ibprovider.com/eng/news/n_181030.html
We have a great piece of news for all users of IBProvider v3 — we have rewritten the latest subsystem inherited from the second version of the provider.
In other words, we have finally fully updated and improved the entire IBProvider v3!
In addition to updating the IBProvider, we released new assemblies of our ADO.NET provider for .NET Standard 2.0 and refreshed the “LCPI OLE DB Services”.
Full news text: http://www.ibprovider.com/eng/news/n_171114.html
Release of “LCPI ADO.NET data provider for OLE DB” v1.1 includes the new DDEX provider (v2) for Visual Studio 2017.
Main features of new DDEX provider
- Based on a new object model (v2), like standard DDEX providers for MSSQL and Oracle
- Packed in VSIX installer
See the short instruction for installation and configuration of DDEX provider in VS2017.
We released three things:
- New update of IBProvider – v3.41.
- New services for IBProvider – “LCPI OLE DB Services”
- New update of our ADO.NET provider – v1.0.7
Full news text: http://www.ibprovider.com/eng/news/n_170511.html
We made the next step for improving of our OLEDB/ADODB/.NET data provider for Firebird and InterBase.
Brief review of changes in new version:
- Removed deprecated features
- Improved steadiness to incorrect configuration of connection
- Added a new feature for error processing [by customer request]
And, of course, new release has passed through load and functional tests. So it is ready for usage in production environment without any unpleasant surprises.
Full news text: http://www.ibprovider.com/eng/news/n_170210.html
Download page: http://www.ibprovider.com/eng/download.html
For getting a Free edition of provider need create an account at our web site: http://www.ibprovider.com/customer/register.php?lang=1
We wrote the new small guide “Using «LCPI ADO.NET Data Provider for OLE DB» with Firebird SQL Server” and offer you acquainted with technological capabilities of our .NET provider.
From this article you can learn, for example:
- How to create multiple transactions within one connection
- How to work with parameters in queries
- How to execute SQL script
Your comments and suggestions are welcome!
We are pleased to announce the second release candidate of our .NET Data Provider for interaction with Firebird and Interbase via IBProvider. By now, we have implemented all the functionality of System.Data.OleDb.
If you want to transfer your .NET projects for FB/IB to the new level of functionality and quality, we recommend you to start using «LCPI .NET Data Provider for OLE DB».
Just look of this DDEX screenshot:
You can get more screenshots and download Ole Db .Net Provider for access to any Interbase or any Firebird database from ADO.Net here: OleDb .Net driver for Firebird >>>
We continue to develop our .NET Provider for OLEDB. In the new build (#1434), we have implemented the methods to obtain database metadata:
- All schemas of the OLEDB Provider
Distinctions compared to standard OLEDB.NET Provider:
- The SchemaGuids schema describes all schemas including SchemaGuids, DbInfoKeywords and DbInfoLiterals.
- The SchemaGuids schema supports restrictions for the Schema column.
Distinctions compared to standard OLEDB.NET Provider:
- The MetaDataCollections schema supports restrictions for the column CollectionName.
- The Restrictions schema supports restrictions for the columns CollectionName and RestrictionName.
- More accurate population of the DataSourceInformation schema.
- More accurate population of the Restrictions schema.
- Caching of data from its own schemas (SchemaGuids, DbInfoKeywords, DbInfoLiterals, …).
- Coherence of information from metadata schemas with the descriptions of the resulting rowset columns and command parameters (ensured by IBProvider).
- Different algorithms of metadata loading for Interbase and Firebird. Including – our provider takes into account the version of the server and the version of database ODS (ensured by IBProvider).
- Caching of OLEDB metadata schemas is carried out on the IBProvider level (see a property «schema_cache»).
- The OleDbSchemaGuid class added with the lists of known OLEDB schema identifiers.
- The OleDbSchemaRestriction class added with the lists of restriction indexes for known OLEDB schemas.
- The OleDbLiteral class added.
- The OleDbMetaDataCollectionNames class added.
- The number of tests and debug structures ensuring the correct work of components increased.
If you are interested in working with stored procedures grouped into PACKAGE, please take a look at the new example for our .NET Provider:
Creation and working with PACKAGE (C#, FB3)
A half year before we product first release of LCPI ADO.NET Data Provider for OLEDB, which became powerful alternative of standard .Net OLE DB Provider and provide advanced opportunities for all Firebird and Interbase users in .Net Framework:
- Automatic generation of command parameters which you do not need to enter manually anymore;
- Named and unnamed parameters, also IN, OUT and IN-OUT parameters;
- Connection pooling and SQL statement pooling which let your code run even faster;
- Nested («nested_trans=true») and distributed (TransactionScope, EnlistTransaction) transactions;
- All data types, including GUID, TIME (Dialect 3), DATE (Dialect 3) and multidimensional arrays;
- The MARS technology which enables working simultaneously with several active DataReader objects;
- And hey, ExecuteScalar now really loads one value only, not the entire record
- Multiple parameter-containing commands in one statement (SQL scripts);
Up to this day LCPI ADO.NET Data Provider for OLEDB was available only in professional version of IBProvider but now you can download it on the download page together with first release of IBProvider in the new year:
You cand download Firebird OLE DB Provider and ADO .Net Data Provider here.
The 3rd part of the Interbase and Firebird Developer’s manual for ADO .Net was published. Examples for DDL queries, metadata schemas and ODBC sequences were presented.