on 2020 Jun 11 2:02 PM
My Environment ... VS2013 with EF 6.0.0 installed and operating with SQLAnywhere 17.0.10.60894 I wanted to spin off a set of EF6 classes to operate with my shiny new SQLAnywhere database.
I finally got the SQLAnywhere data provider to play with VS2013 and the ADO.NET Data Model object. Well on my way to an integrated solution? WRONG.
I was greatly surprised to find the "integrated" product does not support stored procedures? The wizard clearly has these options DISABLED. Having used this wizard with SQL Server, I know the wizard is fully capable of Stored Procedures.
This technology (VS & ADO.NET) has been around for over a decade. approaching 2, I think. so now my question(s) ....
Why would a company such as Watcom/Sybase/iAnywhere/SAP produce a data provider that was incomplete?
Are you trying to make it difficult to use Stored Procedures? Is that a capability you don't want exposed in ADO.NET? I know you can still call a stored procedure using ADO.NET, but we can't get a description of the interface?
I am sure this is a matter of just completing a section of code in the Data Provider. How about an update to fix this hole? Make the product a little easier to use.
User | Count |
---|---|
71 | |
11 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.