|
While testing a deployment of our application, based on the SA10 ADO.NET driver, our deployment popped-up an error message saying ".net framework 4" needs to be installed. On further investigation it seems the problem lies with the sybase ADO.NET driver which needs the full net framework 4 instead of only the "client profile". Does anyone know if this is the case, and if there is any workaround to make the SA10 ado.net driver to work with the net 4 client profile? Thanks in advance |
|
Hello Sergio, Thank you for bringing this to our attention and I'm happy to report that we've removed the dependency to System.Design.dll. The fix will be available in an upcoming EBF. I'll post a comment to this thread when that happens so that you know the build number. Thanks again. José This has been fixed in CR #637333, in builds 10.0.1.4109, 11.0.1.2477, 12.0.0.2565, 12.0.1 GA |
To investigate a bit further i created a very simple solution in Visual Studio 2010. I made a small console application that only connects to a database using the iAnywhere driver. The project was setup to target the net 4 framework client profile. When building, Visual Studio fails and says that the iAnywhere assembly has a dependency on the System.Design.dll, which is not part of the client profile, only the full version. This confirms my suspicion. However, it seems wrong that the iAnywhere assembly should depend on the System.Design dll.
Another update: I just Created a Case with Sybase support, because in my opinion, the ado.net driver should not reference Design components. On further investigations, i found out that the ado.net driver for the net 4.0 version of SQL Anywhere 12 has no dependencies on the full net framework.