Home » Blog

Moving from LightSpeed 2 to LightSpeed 3

Tagged as LightSpeed

LightSpeed 3 has a high degree of compatibility with LightSpeed 2: all existing LightSpeed 2 code should run unchanged against LightSpeed 3. However, there are a few minor changes which LightSpeed 3 users should be aware of.

.NET 3.5 SP1 dependency

LightSpeed now requires .NET 3.5 SP1, though we do still include a build that is compatible with .NET 2.0.

Obsolete APIs

The following APIs have been obsoleted. They are still available and still work in LightSpeed 3, but will raise a compiler warning, and will be removed in a future version.

• LightSpeedContext.Default and LightSpeedContext.BeginUnitOfWork. These were provided to ease migration from LightSpeed 1.x to LightSpeed 2, and are being removed because they don’t work well with LINQ and because many users have found them confusing. (Heck, even we’ve found them confusing.) Use the LightSpeedContext(string configurationName) constructor instead of LightSpeedContext.Default, and the LightSpeedContext.CreateUnitOfWork() instance method instead of LightSpeedContext.BeginUnitOfWork.
• IUnitOfWork.FindOne(object id). This has been renamed to FindById. This is because it was too easy to mistakenly call the FindOne(object) overload when one was intending to call FindOne(Query) or FindOne(QueryExpression).

Logging object

The logging interface, ILogger.LogSql, is declared to receive an object. In LightSpeed 2.x, the object was always a StringBuilder or a string. In LightSpeed 3, the object may also be an instance of the new CommandLog class. The reason for this is to provide structured logging information in case you want to display it in a custom format.

Existing code which calls ToString() or performs a cast to string will not be affected because CommandLog returns the same text as before in these cases. However, code which specifically assumes a StringBuilder will need to be updated.

Add your comments
Posted by Ivan Towlson on 17 December 2009

Leave a Reply