Unless you _really_ need a System.Data.Linq-compatible API, I would suggest
giving up. Instead, focus on getting the open-source EF release working on
Mono, and use that instead.
http://entityframework.codeplex.com/
- Jon
On Jul 31, 2012, at 4:06 AM, Sharique uddin Ahmed Farooqui
W dniu 08.08.2012 14:46, Oskar Berggren pisze:
Or NHibernate, which is working on Mono.
Or use ServiceStack.OrmLite which is also proven
to work very good on Mono and is way easier to use than NH
https://github.com/ServiceStack/ServiceStack.OrmLite
Cheers,
Tomasz Kubacki
Or NHibernate, which is working on Mono.
/Oskar
2012/8/7 Jonathan Pryor jonpr...@vt.edu
Unless you _really_ need a System.Data.Linq-compatible API, I would
suggest giving up. Instead, focus on getting the open-source EF release
working on Mono, and use that instead.
Unless you _really_ need a System.Data.Linq-compatible API, I would suggest
giving up. Instead, focus on getting the open-source EF release working on
Mono, and use that instead.
http://entityframework.codeplex.com/
- Jon
On Jul 31, 2012, at 4:06 AM, Sharique uddin Ahmed Farooqui
Hi,
I have few question regarding linq implementation in mono.
1. Afaik current is based on dblinq
(http://code.google.com/p/dblinq2007), which not much active from some
time, so did mono team created a fork of it or using same code?
2. Sometime back there was a discussion about rewriting linq
Hi,
I have few question regarding linq implementation in mono.
1. Afaik current is based on dblinq
(http://code.google.com/p/dblinq2007), which not much active from some
time, so did mono team created a fork of it or using same code?
Mono is using same code as dblinq2007.
2. Sometime
