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
|
Hei - I'm rewriting a demo application we have in SilverLight,and thought I could use linq to sqlite by including lightspeed. Good idea, but when I try to reference your dll's, I get the "Silverlight projects will only work with SilverLight assemblies". Publish a "SilverLight" dll ? mvh Charles
|
|
|
|
|
Interesting idea. However, the Silverlight runtime doesn't include any of the database access infrastructure of the full .NET runtime, because Silverlight applications, running on the client out on the Internet, will typically not have physical access to a database (at least to Microsoft's "enterprisey" way of thinking, where the database is a centralised, shared resource -- you are of course right that SQLite in isolated storage would be a jolly neat solution for client-side storage). It's not inconceivable that a SQLite (or other "local file" database) provider for Silverlight could be built, in which case we would certainly look at creating a version of LightSpeed to sit over that. But porting SQLite to Silverlight might be quite difficult because the SQLite core code is C-based (System.Data.SQLite puts a managed wrapper around this, but I believe still calls down to native code in the end) and I believe Silverlight does not support interop down to unmanaged code (for security reasons). So I think this is probably a non-starter for now... unless others disagree? |
|
|
|
|
Of course.... sorry, I was completely in "developer" mode... We have developed a C# API for a WITSML server (well data), and have a test app in WPF. We have possibilities to rewrite some web applications using our API, and of course it seemed logical to get into SilverLight, starting with our test app. LINQ is central, we store both test data and server information locallly, so it seemed logical to smack sqlite into a SilverLight app, sticking fast with LINQtoXML/Data/Sqlite/etc (therefore LightSpeed). Now I realize why I had the same problem with Sql Server Compact 3.5.... Oh, well, regardless, it looks like you guys are on a good path, from a DBA viewpoint it's obvious we need to Linq to many Sql sources... Best Regards, Charles
|
|
|
|
