19 Jul 2007
05 Jun 2008
Link to this post
Are they planning to do that?
I do lots of LINQ development, so when I started working on a custom module and found that all the guidance for data access was based on Nolics, I found myself at a junction -- go with Nolics, which was new to me but has lots of Sitefinity support, or go with LINQ, which I am experienced with and like using. I have tentatively opted for the former, because the learning curve is already quite steep for building a decent pluggable module and I didn't want to add more challenges than were necessary.
After working with Nolics a little, I have found it to be very decent. It doesn't have a graphical UI for designing the objects, but the DSL is easy enough. Also, it has the really nice capability to upgrade your database. LINQ can create your initial database structure (DataContext.CreateDatabase) but it does not do structural upgrades to synchronize an old version of the database with the current model. So, if Sitefinity eventually moves to LINQ then they'll also need to address this, either by building a component, buying a component (hopefully with a redistributable development license), or supplying db upgrade scripts (yuck).
One concern I have with Nolics is that I don't know how well it is
supported. There is not a lot of activity in their forum, and it is
surprising that there is no VS2008 support, given that it's been out
now for several months.