home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Plugin Development
Testbuilds for Native MP2 TV - Updated for 10th AE Update 1 (2014-09-13)!
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1096645" data-attributes="member: 82144"><p>Merged, thanks. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>I think the "preferred connection" you mention is just [USER=25430]@gibman[/USER]'s connection string, because I certainly have to modify app.config to connect to my database. IMHO there is nothing really special to protect there. Either way, surely it would be good to have an example SQLite connection string like we already have for MySQL, SQL Server and SQL Server CE?</p><p>[collapse]</p><p> <connectionStrings></p><p> <!--</p><p> for MYSQL use:</p><p> <add name="Model" connectionString="metadata=res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.csdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Mediaportal.TV.Server.TVDatabase.EntityModel.Model.MySQL.ssdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.msl;provider=MySql.Data.MySqlClient;provider connection string=&quot;server=localhost;User Id=root;database=TVE35;password=MediaPortal;Persist Security Info=True&quot;" providerName="System.Data.EntityClient" /></p><p></p><p> for MS SQL use:</p><p> <add name="Model" connectionString="metadata=res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.csdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Mediaportal.TV.Server.TVDatabase.EntityModel.Model.MSSQL.ssdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.msl;provider=MySql.Data.MySqlClient;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=localhost\SQLEXPRESS;Initial Catalog=TVE35;User ID=sa;Password=MediaPortal;MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" /></p><p></p><p> for MS SQL CE (MP2) use:</p><p> <add name="Model" connectionString="metadata=res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.csdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Mediaportal.TV.Server.TVDatabase.EntityModel.Model.MSSQLCE.ssdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.msl;provider=System.Data.SqlServerCe;provider connection string=&quot;Data Source='C:\ProgramData\Team MediaPortal\MP2-Server\TVE35.sdf'; Default Lock Timeout=30000; Max Buffer Size = 2048; Max Database Size = 1024;&quot;" providerName="System.Data.EntityClient" /></p><p> -->[/collapse]</p><p></p><p>I had assumed (maybe wrongly?) that when TVE 3.5 gets a standalone installer it would be desirable to make it possible to select SQLite as one of the DB options like we have with MySQL and SQL Server for TVE 3. In other words, it might not only be MP2 that uses SQLite. Therefore we would need SQLite in the packages.config.</p><p></p><p>On that note, I don't know if you saw already: I've now removed the ExternalBinaries directory and replaced it with the official NuGet packages for EF and MySQL. They're included in the EntityModel project packages.config... and I'd do the same with SQLite... and SQL Server CE if binaries are/were also required for that.</p><p></p><p>...or have I misunderstood something?</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1096645, member: 82144"] Merged, thanks. :) I think the "preferred connection" you mention is just [USER=25430]@gibman[/USER]'s connection string, because I certainly have to modify app.config to connect to my database. IMHO there is nothing really special to protect there. Either way, surely it would be good to have an example SQLite connection string like we already have for MySQL, SQL Server and SQL Server CE? [collapse] <connectionStrings> <!-- for MYSQL use: <add name="Model" connectionString="metadata=res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.csdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Mediaportal.TV.Server.TVDatabase.EntityModel.Model.MySQL.ssdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.msl;provider=MySql.Data.MySqlClient;provider connection string="server=localhost;User Id=root;database=TVE35;password=MediaPortal;Persist Security Info=True"" providerName="System.Data.EntityClient" /> for MS SQL use: <add name="Model" connectionString="metadata=res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.csdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Mediaportal.TV.Server.TVDatabase.EntityModel.Model.MSSQL.ssdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.msl;provider=MySql.Data.MySqlClient;provider=System.Data.SqlClient;provider connection string="Data Source=localhost\SQLEXPRESS;Initial Catalog=TVE35;User ID=sa;Password=MediaPortal;MultipleActiveResultSets=True"" providerName="System.Data.EntityClient" /> for MS SQL CE (MP2) use: <add name="Model" connectionString="metadata=res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.csdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Mediaportal.TV.Server.TVDatabase.EntityModel.Model.MSSQLCE.ssdl|res://Mediaportal.TV.Server.TVDatabase.EntityModel/Model.msl;provider=System.Data.SqlServerCe;provider connection string="Data Source='C:\ProgramData\Team MediaPortal\MP2-Server\TVE35.sdf'; Default Lock Timeout=30000; Max Buffer Size = 2048; Max Database Size = 1024;"" providerName="System.Data.EntityClient" /> -->[/collapse] I had assumed (maybe wrongly?) that when TVE 3.5 gets a standalone installer it would be desirable to make it possible to select SQLite as one of the DB options like we have with MySQL and SQL Server for TVE 3. In other words, it might not only be MP2 that uses SQLite. Therefore we would need SQLite in the packages.config. On that note, I don't know if you saw already: I've now removed the ExternalBinaries directory and replaced it with the official NuGet packages for EF and MySQL. They're included in the EntityModel project packages.config... and I'd do the same with SQLite... and SQL Server CE if binaries are/were also required for that. ...or have I misunderstood something? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
Testbuilds for Native MP2 TV - Updated for 10th AE Update 1 (2014-09-13)!
Contact us
RSS
Top
Bottom