Reply to thread

Message

<blockquote data-quote="MJGraf" data-source="post: 1033550" data-attributes="member: 17886">Just a short note so that it is not forgotten:&nbsp;SQLite does not work with SlimTV Native (yet), because SlimTV Native uses TVE3.5, which in turn uses Entity Framework 4, which finally requires three methods called DatabaseExists, CreateDatabase and DeleteDatabase in the respective ProviderService when you use CodeFirst (which TVE 3.5 does).&nbsp;These methods are not yet implemented for System.Data.SQLite.&nbsp;MS itself has published a sample on how to implement these methods. The <a href="http://entityframework.codeplex.com/SourceControl/latest#samples/Provider/SampleEntityFrameworkProvider/ProviderServices.cs" target="_blank">methods themselves </a>are quite straightforward, but only because the main work is transferred into an object called <a href="http://entityframework.codeplex.com/SourceControl/latest#samples/Provider/SampleEntityFrameworkProvider/DdlBuilder.cs" target="_blank">DdlBuilder</a>. Although this object's content is a bit more complicated, it doesn't really seem impossible to adapt this code for SQLite. Seems just like a few hours of comparing the SQL statements built by this class with the SQLite SQL syntax...&nbsp;Only problem: The System.Data.SQLite.SQLiteProviderServices class is internal and sealed. Does anyone of the C# cracks around knows a (potentially very dirty) hack to nevertheless inherit from that object just by using the DLL? I don't want to setup a build environment for the whole System.Data.SQLite project...&nbsp;Thanks!</blockquote>

[QUOTE="MJGraf, post: 1033550, member: 17886"] Just a short note so that it is not forgotten: SQLite does not work with SlimTV Native (yet), because SlimTV Native uses TVE3.5, which in turn uses Entity Framework 4, which finally requires three methods called DatabaseExists, CreateDatabase and DeleteDatabase in the respective ProviderService when you use CodeFirst (which TVE 3.5 does). These methods are not yet implemented for System.Data.SQLite. MS itself has published a sample on how to implement these methods. The [URL='http://entityframework.codeplex.com/SourceControl/latest#samples/Provider/SampleEntityFrameworkProvider/ProviderServices.cs']methods themselves [/URL]are quite straightforward, but only because the main work is transferred into an object called [URL='http://entityframework.codeplex.com/SourceControl/latest#samples/Provider/SampleEntityFrameworkProvider/DdlBuilder.cs']DdlBuilder[/URL]. Although this object's content is a bit more complicated, it doesn't really seem impossible to adapt this code for SQLite. Seems just like a few hours of comparing the SQL statements built by this class with the SQLite SQL syntax... Only problem: The System.Data.SQLite.SQLiteProviderServices class is internal and sealed. Does anyone of the C# cracks around knows a (potentially very dirty) hack to nevertheless inherit from that object just by using the DLL? I don't want to setup a build environment for the whole System.Data.SQLite project... Thanks! [/QUOTE]

Verification