-
as seen on Stack Overflow
- Search for 'Stack Overflow'
While there's lots to like about DataObjects.NET, I've found help resources to be a lean, and can't find a solit example of using DataObjects.NET with RDBMS generated primary keys. It would seem as though D4O won't do inserts against SQL Server unless it's in controll of the key.
Has anyone solved…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I am looking for ORM frameworks, came along to NHibernate, Genome, L2S, Entity Framework and now the DataObjects.NET.. So far a I read the documentation it seems pretty cabable, but have you ever tried this ORM?
Any issues/bugs with DO.NET would be approciated :)
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I would like to see your experience with popular ORM tools outhere, like NHibernate, LLBLGen, EF, S2Q, Genom-e, LightSpeed, DataObjects.NET, OpenAccess, ...
From my exp:
- Genom-e is quiet capable of Linq & performance, dev support
- EF lacks on some key features like lazy loading, Poco support…
>>> More
-
as seen on Geeks with Blogs
- Search for 'Geeks with Blogs'
short answer: Quite probably, as SQL Azure is very similar to SQL Server longer answer: Object Relational Mappers (ORMs) that work with SQL Server are likely but not guaranteed to work with SQL Azure. The differences between the RDBMS versions are small – but may cause problems, for example in tools…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
One advantage that comes to my mind is, if you use Poco classes for Orm mapping, you can easily switch from one ORM to another, if both support Poco.
Having an ORM with no Poco support, e.g. mappings are done with attributes like the DataObjects.Net Orm, is not an issue for me, as also with Poco-supported…
>>> More
