Hello,
I have been a user of dotConnect for PostgreSQL for quite some time and I'm very happy with your product.
We are planning to base our next product on Mono and that generated some questions.
Could someone help? thanks...
Is LinqConnect supported on Mono?
Is Devart version of Entity Framework supported on Mono?
If both are supported which one is the recommended one for Mono in terms of performance and robustness?
Why should I choose LinqConnect over Devart Entity Framework? I know Linq to SQL has a simpler design, so I hope the implementation can perform faster, is that true on Devart versions of these frameworks?
LinqConnect on Mono
-
StanislavK
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Concerning your questions:
1) We did not perform complete testing of the LinqConnect functionality under Mono, but simple test projects run successfully on the latest Mono versions.
2) As far as we know, there is no implementation of the main Entity Framework assemblies (e.g., System.Data.Entity) for Mono. Since the dotConnect for PostgreSQL support for Entity Framework is based on these assemblies, it cannot be used under Mono.
3) Generally, LinqConnect should be faster than Entity Framework. If you are interested in performance of some specific scenarios, please describe these scenarios.
1) We did not perform complete testing of the LinqConnect functionality under Mono, but simple test projects run successfully on the latest Mono versions.
2) As far as we know, there is no implementation of the main Entity Framework assemblies (e.g., System.Data.Entity) for Mono. Since the dotConnect for PostgreSQL support for Entity Framework is based on these assemblies, it cannot be used under Mono.
3) Generally, LinqConnect should be faster than Entity Framework. If you are interested in performance of some specific scenarios, please describe these scenarios.
Thanks for your quick response...
So, I will be trying LinqConnect and see how it goes.
The other option I'm considering is NHibernate combined with your Entity Developer designer. I could not find any specifics about which version of NHibernate you support or recommend?
Are your additions to NHibernate supported and/or tested under Mono?
In terms of ADO.NET drivers I guess that your designer will support any third party driver supported by NHibernet, is that right? I will be developing for PostgreSQL and MySQL; I already have your driver for the first one, but I will like to know if I can use any other third party MySQL driver with your Designer?
Thanks
So, I will be trying LinqConnect and see how it goes.
The other option I'm considering is NHibernate combined with your Entity Developer designer. I could not find any specifics about which version of NHibernate you support or recommend?
Are your additions to NHibernate supported and/or tested under Mono?
In terms of ADO.NET drivers I guess that your designer will support any third party driver supported by NHibernet, is that right? I will be developing for PostgreSQL and MySQL; I already have your driver for the first one, but I will like to know if I can use any other third party MySQL driver with your Designer?
Thanks
-
StanislavK
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Entity Developer supports the latest versions of NHibernate (e.g, versions 3.0-3.2), and we plan to support the new versions when they are released. Compatibility with prior NHibernate versions was not tested.
As for the Mono support, Entity Developer is a Windows application and integrates into Visual Studio only; thus, you can only generate models on Windows machines and use them in your applications being developed with Mono. Provided that the NHibernate runtime is compatible with Mono, it should be possible to use the models created by Entity Developer under Mono as well. You can address the question on the NHibernate-Mono compatibility to the NHibernate or Mono community.
Entity Developer does support arbitrary third-party data providers (for NHibernate models).
Feel free to contact us if anything is unclear.
As for the Mono support, Entity Developer is a Windows application and integrates into Visual Studio only; thus, you can only generate models on Windows machines and use them in your applications being developed with Mono. Provided that the NHibernate runtime is compatible with Mono, it should be possible to use the models created by Entity Developer under Mono as well. You can address the question on the NHibernate-Mono compatibility to the NHibernate or Mono community.
Entity Developer does support arbitrary third-party data providers (for NHibernate models).
Feel free to contact us if anything is unclear.