Living in the Tech Avalanche Generation

Ayende created Rhino.Queues.Storage.Disk a while ago and followed with Rhino.Queues and left it to the community to join them together. I would love to have transactional ‘store and forward‘ available as a design choice that incorporates Silverlight and I’m wondering if these two abandoned children of Ayende’s might provide the basis of an answer? Maybe not. I can see that wrapping Isolated Storage read / write operations with some kind of veneer might be useful however really what’s required here is a solution that enlists in transactions (System.Transaction) thus  making our ’store and forward’ pattern safe and durable. Offline Silverlight with MSMQ? Perhaps, but for now that’s a hack. What about localhost WCF with a database behind it? Sure there are ways and means and somehow this is something I don’t see Microsoft investing in as it’s probably a bit too ‘fringe’ as a requirement, so it’s probably going to be up to the community. Personally I will probably wait till Silverlight is working offline (by design) and reconsider durable storage with Silverlight until then. In the meantime however I am absolutely loving working with XAML based UI in both Silverlight and WPF and going back to Windows Forms is not something likely to ever happen. Oddly, when I open a WinForm application in VS.Net I get the strangest feeling, almost like the one I used to have when opening the VB6 IDE after having developed in .NET for a few years. Must be sign?