I hope this answers all your points – thanks for the feedback :-)

1. No support here, we haven’t tried it and I’m doubtful it would work off the bat anyway. I’d like to see far more growth from Monotouch before we would start looking at that space I’m sorry.

2. LS3 will work with Azure. We’re very interested supporting cloud platforms which is why we’re still the only .NET ORM that supports SimpleDB :-) In fact we had a demo of LightSeed working with Azure at Tech Ed New Zealand this year.

Expect to see further additions of other data stores and improved support for existing ones post 3.0. If there is a specific feature you’d like to see, please let us know.

3. We’re discussing this with Ayende already. He’s working on how he will support the various other ORMs at the moment and once he’s got a pattern in place we’ll work together to get LightSpeed supported.

4. We added support for only updating changed columns in LS3. This applies only when optimistic concurrency is enabled however to ensure you don’t accidentally create invalid entities (meaning you must have a version field).

In memory testing with SQLite is possible with almost any ORM that supports SQLite because it’s just a connection string parameter. Having said that, I believe in memory testing with SQLite is a weak approach to accelerating tests (unless you’re live system is SQLite) due to the limitations you’ll run into when using SQLite (limited type support, FK issues, etc).

The testing enhancements we have added in 3.0 will provide an easier mechanism for building a UnitOfWork in memory that you pre-load with Entities that you wish to be returned. This means you won’t run into the issues using a different database to the one you’re using in production, avoids testing the database when you should be testing your code and improves performance. We always appreciate feedback on this area however because there are plenty of great ideas to be had :-)

Thanks for your feedback!

My preferences for ORM are also changing constantly, so now I’m looking for few “extras”, any plans of supporting these?
1. Monotouch platform? (“Lightspeed lite” would be great, there’s sqlite only there but sadly no reflection, don’t know how hard would it be to port it due to missing ado.net implementation as of yet)

2. Azure SQL i.e. SDS support? Cloud computing is becoming popular, and although we can have REST with MS Azure databases, having first-class support for SDS protocol would be awesome (so far only MS product has that).

3. ORM profiler? Oren Eini (aka Ayende Rahien) latest posts showed, that his profiler can be extended by supporting other ORMs. And if there’s such a “non-orm-ish” product as Linq to SQL (good but with so many limitation one wonder) I’m curious if there couldn’t be some collaboration to also support Lightspeed (as he is supporting competitive product from Mr. Bauma).

4. Last but not least, the other day in 2008 I had few gripes, like UPDATE hitting every column of a table although only one changed etc, any improvement on performance front?

Awesome product anyway, I’m sure, my 2nd most favourite ORM, it’s because it was harder to go with TDD w/o POCO support in Lightspeed, so I’m eager for more info about the testing…is in memory sqlite possible?

Thanks for your comment.

As you can see, 3.0 was a fairly large undertaking with what we are already delivering. We have not included any additional support for WCF services beyond what we already provide (generating DTO’s + mapping them and support for the standard WCF serialization).

Work around improvements in this domain are planned for post LightSpeed 3.0.

I hope that helps.