This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm looking at building an application that can be hosted on Azure or on-premise. I'm also interested in using Lightspeed based on the reviews I've read. From what I've read on the forums, there does not appear to support for Storage Tables yet, nor any effort to add that support, although you would like to support Azure once its form is more mature (my paraphrasing). However, I thought maybe SQL Azure would work with little or no modification because SQL Azure is supposed to be compatible with SQL Server 2008 (my simplification). Have you tried Lightspeed with SQL Azure? Have you heard of anybody using Lightspeed with SQL Azure? Do you have plans for supporting Storage Tables in Azure? Could you share them? I'm going to be actively working on this, and would be happy to work with you on any new feature you'd like to try out in order to get this working. I could come up with a solution that uses Lightspeed for on-premise and EF for Azure, but I'm not sure I want to.
|
|
|
|
|
LightSpeed currently works just fine with SQL Azure as far as we know since SQL Azure is basically just SQL Server 2008 and we dont hit any of the limitations in the CloudDB based version; however this is not something we currently directly test again, more it is something we have tested in the context of samples and demoware. I am not currently aware of any production use of this, or anyone who is using LightSpeed within an Azure app targeting SQL Azure, however we are likely to be looking at this in the near future. As for Azure Table Storage - this is not something we are currently looking at, but if there was enough interest we would be happy to consider adding this :)
Jeremy |
|
|
|
