We want to notify about two updates of IBProvider, which finalize migration from v3 to v5.
Improved integration of provider subsystems.
Removed obsolete OLE DB properties.
We offer 12+4 months of support and upgrades to anyone, who purchases licenses for IBProvider (32/64bit) until the end of March 2019.
Thanks&Regards, IBProvider Team.
We are released new update of our ADO.NET provider for OLE DB, which allows the work with Firebird and InterBase from .NET application through IBProvider.
Description of change
When connecting to the Firebird, InterBase and Yaffil databases, the «ISC:DatabaseDialect» and «ISC:ConnectionDialect» columns are available in the «DataSourceInformation» metadata schema.
This information is taken from the information properties of IBProvider:
«IB Database Dialect» and «IB Connection Dialect», respectively.
The full list of columns in the DataSourceInformation schema is defined in the static class OleDbMetaDataCollectionColumnNames.DataSourceInformation.
You may get our ADO.NET provider from
IBProvider site and from NUGET site.
Regards, IBProvider Team.
We are proud to introduce the fifth version of our basic product for working with Firebird and InterBase.
IBProvider v5 inherits all the best from IBProvider v3 and dramatically improves the quality of implementation of the OLE DB components.
For the last few years, the main development line of IBProvider was fixing problems that prevented its stable operation. First of all, we had to fix problems not related to the provider itself — we
rewrote the client for Firebird and the standard pool of OLE DB connections. It took a lot of time and resourses, but it was worth it.
Now the time has come to get to IBProvider itself.
Instead of local fixes, within the support of the third version we redesigned the inner infrastructure of the OLE DB components of IBProvider taking into account the entire experience gained over the last years. In part, the ideas were taken from
our ADO.NET provider.
The main qualities of IBProvider v5 are reliability and fail safety…
Read full text of IBProvider v5 release.
With Best Regards, IBProvider Team.
We are pleased to announce the new releases of our components for working with Firebird and InterBase.
https://www.ibprovider.com/eng/news/n_181218.html IBProvider v3.54 and “LCPI OLE DB Services” v1.6
ADO.NET Provider v1.9.1
Most likely this is the last updates in 2018 year. New releases will be in next year. We already work on these.
So, we want to say thanks to all our customers and users. Really – THANKS!
We wish you only the best in the New 2019 Year!
We have released a new version of our ADO.NET provider, which fixes some problems with the DDEX providers:
Plus, we uploaded to YouTube the video:
“Setup of DDEX provider for LCPI ADO.NET Provider into Visual Stidio 2017”.
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:
For fans only:
For the first time, we managed to perform all IBProvider system tests applicable to Firebird v3 in one run. This took 26 days and a ten-core processor.
Full note text:
We have released an update of IBProvider, which has the solution for error with code 8152 of MS SQL Linked Server.
Short annotation of this problem – MS SQL has the problem with processing of object descriptions in metadata schemas.
New provider allows you do not publish object descriptions in schemas.
You may turn off publication of object descriptions to speed up the process of loading metadata schemas as a whole.
We glad to inform you about news of
IBProvider [Native OLE DB Provider for InterBase and Firebird] development cycle.
A support of Firebird 3.0.4 improved
A code optimization performed
Link to latest press-release:
IBProvider and «Registration Free COM»
We wrote a new document about usage IBProvider without registration in Windows registry:
Recommended for reading to everyone who distributes IBProvider as part of own applications.
With Best Regards,
In this note we would like to inform you about running 6.7 million various tests for blobs. On our scale, it is a big testing. Usually we run each IBProvider update through 0.7 million tests.
Performing these 6.7 million tests in one thread would take 150 days. Parallel run in 10 threads reduced this time to 15 days.
We won’t bore you with details and will provide only key information.
Read full text: