cancel
Showing results for 
Search instead for 
Did you mean: 

Fully managed ADO.NET driver written in 100% pure C#

Former Member
0 Kudos

Are there any plans for implementing fully managed ADO.Net provider in future. As Microsoft is planning make .Net cross platform, having cross platform provided implemented purely in managed .Net code will be of great help.

Accepted Solutions (0)

Answers (1)

Answers (1)

jeff_albion
Employee
Employee
0 Kudos

Hello Venkata,

This question was previously asked on our forum here - we do not have any current cross-platform support of .NET (Mono or otherwise). We do have support for many other APIs that can be used on Mac / Linux / Unix / etc.

However, if you have a compelling business case for using .NET on non-Windows platforms, our product management team would certainly like to hear about it. You can message Jason Hinsperger with any product support feedback you would like to pass on.

Thanks,

Jeff Albion

SAP Active Global Support

Former Member
0 Kudos

Hi Jeff,

We do have  a business case other than cross-platform.   One of our .Net web application runs in the Azure cloud with SQLAnywhere as the backend.  

We are using the Auto Scale feature. Azure creates a new web roles(PAAS) on demand (Creates a  new windows machine and deploys the application on the fly and adds to the cluster). 

Since  .NET provider requires native dl'ls from  the Sybase Anywhere client, we have to  bundle the client installer as part our package. The installer is failing at times causing Auto-Scaling very difficult.

Having  a fully managed .NET provider will eliminate the need of installing the SQLAnywhere client on  the new windows machines created on the fly.

Thanks

Venkat

jeff_albion
Employee
Employee
0 Kudos

Hello Venkata,


The installer is failing at times causing Auto-Scaling very difficult.

Can you maybe clarify on how your installer is failing specifically, based on the fact that it is a mixed provider? Are you getting an error message?

Have you reviewed the notes for deploying the ADO.NET driver in the documentation? ( http://dcx.sap.com/index.html#sa160/en/dbprogramming/deploying-adonet-deploy.html ).

We have had many customers deploy the SQL Anywhere ADO.NET provider successfully over a variety of installation methods. The included Deployment Wizard which creates an MSI (see the documentation), our separate SQL Anywhere client install ( ), and the ability to package for .NET ClickOnce deployments (see the documentation and the wiki), are all successful to install and set up the provider in many Windows environments.


Having  a fully managed .NET provider will eliminate the need of installing the SQLAnywhere client on  the new windows machines created on the fly.

Whether the interface is managed or unmanaged, you will still need to make the SQL Anywhere ADO.NET assemblies available. The only difference with the unmanaged components is that you have to include extra binary (.DLL) files in your deployment, which is a common requirement for many installs.

Regards,

Jeff Albion

SAP Active Global Support