Feedback
Did this article resolve your question/issue?

   

Article

Are the Connect for ADO.Net 4.2 providers supported with Visual Studio 2017?

Information

 
TitleAre the Connect for ADO.Net 4.2 providers supported with Visual Studio 2017?
URL NameAre-ther-Connect-for-ADO-Net-4-2-providers-supported-with-Visual-Studio-2017
Article Number000183234
EnvironmentProduct: Connect for ADO.Net all providers
Version: 4.2
OS: Windows
Database: All supported databases
Application: All supported applications
Question/Problem Description
Are the Connect for ADO.Net 4.2 providers supported with Visual Studio 2017?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Currently (5/1/2017) Visual Studio 2017 is not certified with the Connect for ADO.Net 4.2 providers. As of 08/01/2018, there are no plans to certify 4.2 with Visual Studio 2017.
Workaround
Notes
Last Modified Date8/1/2018 2:00 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.