2008-06-17

ALite 2.10

Another ALite update, which fixes a few bugs and adds in database transactions (which may or may not be utterly useless, depending on how you structure your DB calls). I can’t think of anything else I want to add to it that could offer anything I’d want to use regularly, so I declare it finished. The only two areas of functionality I’m tempted to remove (basic rule system and the parameter-less version of the DataAccess constructor) are very handy, so they have to stay.

Fixes include swapping to generic collections, where possible, for minor speedups; improved disposal of DataAccess objects; parameters now get passed when inline SQL is executed; and I’ve fixed a handful of FxCop warnings. Full changelog is in the archive.

I started writing some more useful documentation until I realised that documenting a data access framework is immensely boring. The only thing more boring is reading data access framework documentation, so I gave up. I did take a look at “Why’s (Poignant) Guide to Ruby” for inspiration, but it quickly became apparent that I was automatically skipping over the cartoons of foxes discussing chunky bacon in order to get straight to the programming bits.

Download it from the SourceForge page should you find yourself in the unenviable position of needing a miniature framework for interacting with an SQL database in .NET:

ALite

Comments

ant.simianzombie.com » ALite Changes on 2009-10-07 at 22:47 said:

[...] C#.NET framework for creating objects that interact with databases, has had a few updates. Back in June last year I complained that I wasn’t happy with the basic validation system. I have refactored this [...]