Microsoft stops developing Oracle Client in ADO.NET 4
Translation of an article from the official blog.
As part of our long-term strategy development for ADO.NET, we conducted a series of discussions with our customers, internal and external partners, and MVPs to better coordinate our development efforts and make sure that we provide the right technology in line with the primary needs of our customers. One of the key intentions of these discussions and related research was to understand the needs and requirements of customers, to develop applications using Oracle System.Data.OracleClient (OracleClient). OracleClient is an ADO.NET provider for Oracle, developed by Microsoft and supplied as part of the .NET Framework.
We learned that a significant majority of customers use our partners' ADO.NET providers for Oracle, with regularly updated support for Oracle releases, as well as the availability of new features. In addition, many third-party vendors are able to consistently provide the same level of quality and support that customers expect from Microsoft. This proves that our partners are able to provide good support for our technologies and the strength of our partner ecosystem. Even if we make a significant investment in ADO.Net OracleClient to align it with the providers of our partners, our customers have no good reason to switch to ADO.Net OracleClient.
')
Decision
After careful consideration of all options, and conversations with our clients, partners and MVP, it was decided to exclude the OracleClient from the ADO.NET roadmap.
Recommendations and guidelines:
System.Data.OracleClient will be available in the upcoming release 4.0. NET Framework, however, it will be marked as deprecated. This will have no impact on existing applications, and these applications will continue to work as expected. Development of new applications that use OracleClient will be supported, however, warnings will be shown if applications are compiled on .Net 4.0. After compilation, no error and warning messages will be output during operation. We strongly encourage customers to use our partners' ADO.NET providers for Oracle instead of continuing to use Microsoft OracleClient in developing new applications.
Microsoft will continue to provide fixes for critical issues in System.Data.OracleClient as per standard support policy for .Net Framework 4.0. We will also continue to fix critical bugs in future service packs for .NET Framework 4.0.
As part of our long-term strategy development for ADO.NET, we conducted a series of discussions with our customers, internal and external partners, and MVPs to better coordinate our development efforts and make sure that we provide the right technology in line with the primary needs of our customers. One of the key intentions of these discussions and related research was to understand the needs and requirements of customers, to develop applications using Oracle System.Data.OracleClient (OracleClient). OracleClient is an ADO.NET provider for Oracle, developed by Microsoft and supplied as part of the .NET Framework.
We learned that a significant majority of customers use our partners' ADO.NET providers for Oracle, with regularly updated support for Oracle releases, as well as the availability of new features. In addition, many third-party vendors are able to consistently provide the same level of quality and support that customers expect from Microsoft. This proves that our partners are able to provide good support for our technologies and the strength of our partner ecosystem. Even if we make a significant investment in ADO.Net OracleClient to align it with the providers of our partners, our customers have no good reason to switch to ADO.Net OracleClient.
')
Decision
After careful consideration of all options, and conversations with our clients, partners and MVP, it was decided to exclude the OracleClient from the ADO.NET roadmap.
Recommendations and guidelines:
System.Data.OracleClient will be available in the upcoming release 4.0. NET Framework, however, it will be marked as deprecated. This will have no impact on existing applications, and these applications will continue to work as expected. Development of new applications that use OracleClient will be supported, however, warnings will be shown if applications are compiled on .Net 4.0. After compilation, no error and warning messages will be output during operation. We strongly encourage customers to use our partners' ADO.NET providers for Oracle instead of continuing to use Microsoft OracleClient in developing new applications.
Microsoft will continue to provide fixes for critical issues in System.Data.OracleClient as per standard support policy for .Net Framework 4.0. We will also continue to fix critical bugs in future service packs for .NET Framework 4.0.
Source: https://habr.com/ru/post/62437/
All Articles