I have seen some docs around suggesting that monodroid could support Entity Manager. Is this true? I remember reading that monodroid was based on 2.0 framework, and entity framework seems to be a 3.5 and above tecnology so I'm a bit confused here. Do anybody have any experience with this?.
Thanks in advance.
Well, after spending around an hour looking for this information, I foudn the answer as soon as I posted the message D.
It is not supported. Features available to monodroid can be checked here:
http://support.xamarin.com/customer/portal/articles/375825-how-does-mono-compare-to-net-4-0-
Related
Could anybody provide some details on "how entity framework actually works" or point me to a web site? I dont find any somehow.
I'm affraid that it is so complex that you can start only here or buy this.
I would highly recommend Julie Lerman's book Programming Entity Framework (she's working on the 2nd edition which will cover EF v4) and in the meantime, check out her Learn Entity Framework web site for hints, tips, tutorial and much more.
She's also doing a series of introductory screencasts at Pluralsight On-Demand training, which is not free, but online training well worth the price of a subscription.
Also check out the ADO.NET team blog for interesting tidbits about EF from time to time.
Does anyone has experience with plinqo 4?
what are the benefits vs EF 4?
A good answer to this is on the PLINQO site itself
http://www.plinqo.com/why-plinqo.ashx
I looked at EF, NHibernate and Subsonic and finally rested with PLINQO as it seems to have the best bits of all the ORMS without too much of the bloat. Plus sitting on top of LINQ2SQL its pretty fast.
You can only really judge this by trying it yourself but I would save yourself some time and try PLINQO before EF.
Yes, we use PLINQ, it's Extremley good and provides out of the box support for ADO.NET Data Services and WCF Data Contracts.
PLINQO has better serialization across the wire options as well.
I've been rolling my own object mapping system for over ten years and my current .NET version is pretty stable and I understand it. I've always kept a watchful eye on commercial developments in this area such a Hibernate but I've stuck with what I know.
However, I keep hearing more about Entity Framework and wondered whether it's time to investigate with a view to replacing my own home-grown system with Entity Framework. Microsoft has had a bit of a checkered history in this field with ObjectSpaces getting cancelled. I assume that project has become Entity Framework. Why did they cancel ObjectSpaces and have they got around the problems in Entity Framework? Is Entity Framework "better" than Hibernate?
Cheers, Rob.
I saw a demo of the entity framework ver 4.0 that will be released with Visual Studio 2010. Looked like it would make you very productive. I think this version will make it main stream for .net developers. More info here.
NHibernate has been around a lot longer and i think that if any .NET mapping library has reached critical mass, nHibernate would be it. Have you checked it out?
P.S. NHibernate is also a port from Hibernate which is THE mapping library for Java. That's a petty good pedigree.
I'd like to hear from people who are using EF in production, or made a valid attempt to do so.
I saw the When NOT to use the Entity Framework question on this site. I also read Vote of No Confidence. If you played with Entity Framework and decided not to use this, I don't want to hear from you.
I understand that EF is not mature as NHibernate or some other framework. Unfortunately, in my company, people who make decisions don't want to use the open source projects. Don't ask me why, because I'd like to know it myself.
Yes, we use it in production. V1 is in the field, V2 is on the way. It works really well for us so far. Did you have any other questions?
Absolutely.
I'm at TechEd this week, spending a lot of time at the Entity Framework booth, and I've had lots people who are using EF in anger come up and ask me for help and advice.
Alex
So far I did not like EF. Although I liked the tools and how easy it was to create certain types of mappings and relations, Other types were a pain and the Linq support in EF wasn't so great (couln't create my own filter extension methods).
Is the new EF in .Net 4.0 better. Given what I have stated so far is there a chance I will like it.
The reson I ask this is because I use linq2sql a lot and do not like the feeling that the platform I am using is about to go obsolete. I would like to upgrade to something that is as similar as possible to what I already have.
Thanks for your opinions
It's only an opinion, but I believe that the new EF will be much improved. They will almost certainly have some kind of migration path from Linq to SQL. Whether it will look like Linq to SQL is another story. The two tools have somewhat different philosophies.
While EF will be designed for enterprise scenarios, it is my hope that the next version will still be lightweight enough to serve as an adequate replacement for L2S in small application scenarios.
I am really optimistic about EF 4.0 from all that I have seen thus far. The beta release is already available to MSDN subscribers and it addresses a lot of the concerns around POCO, Persistence Ignorance, N-Tier support and all that. I continue to recommend reading the ADO.NET team blog as a great resource for what's changed.
You can't compare it to the first release because this is a very big overhaul and a lot has changed.
That said, initial adopters always get the worst of it because they are the first to run into bugs and new problems while the late comes can benefit from the lessons learnt by the early adopters.
There has been a lot of improvements. I have ran in to a couple of strange issues but nothing unsolvable yet. It took me a few hours to understand how POCO works meaning they spent a lot of. I recommend you download VS2010 and play around with it yourself!
Have a look at this presentation, and you will know why EF worth your time.
How to Think Like the Entity Framework Presentation: http://blogs.teamb.com/craigstuntz/2009/09/11/38394/