The .NET community is the best development community ever.
How do I know that? Because they ask the best questions!
Here are two really important questions that we have been asked concerning PLINQO for Entity Framework that I wanted to call some extra attention to:
What is the advantage of using PLINQO EF instead of standard Entity Framework?
In 1.0 the primary goal was to improve the regeneration story of Entity Framework, thus making it easy to update and sync data and code changes. The entities are pretty much equivalent, but the PLINQO query extensions greatly improve and simplify the composition of queries.
With future versions there will be more features brought in from the PLINQO for L2S feature set. This will include built in caching, auditing, enhanced serialization, possibly WCF and DataServices support, and hopefully batch/future queries!
What are the benefits, if any, of moving to PLINQO EF over PLINQO L2S?
Such benefits are not there yet, but will be. The primary reason to migrate right now would be to inherit the benefits that standard EF has over L2S, most notably is its multiple database support (so more than just SQL Server).
There will be a simple migration path between the two versions of PLINQO, but the bottom line is that PLINQO EF is not ready for that yet. It is still in beta, and is simply not yet as feature complete as PLINQO L2S. It’s going to take one or two releases until we get there, but we will get there!