1

Topic: SQL Server CE - how to understand where a problem?

Actually, selected SQL Server CE as basic for a program. It is possible to switch, but for not skilled it the automatic machine costs. Selected as least  for EF for which of a box all works (for SQLite it is necessary to create manually tables, and it to me is not pleasant). But there is one splinter. On my computer all works bright, is connected for 1 second And on other computers with the same surrounding, with faster iron, the same Windows version and.Net, 4.0 SP 1 - connection happens to the same version SQL CE 5-7 seconds In what there can be a splinter? As though it is better to find?

2

Re: SQL Server CE - how to understand where a problem?

Hello, Shmj, you wrote: S> Actually, selected SQL Server CE as basic for a program. It is possible to switch, but for not skilled it the automatic machine costs. Selected as least  for EF for which of a box all works (for SQLite it is necessary to create manually tables, and it to me is not pleasant). And questions to set or  the religion does not allow? I do not know what at you , but you do not check - in SQLite even migrations are supported. Enough in designer Configuration to specify public Configuration () {SetSqlGenerator ("System. Data. SQLite", new SQLiteMigrationSqlGenerator ());}

3

Re: SQL Server CE - how to understand where a problem?

Hello, Shmj, you wrote: S> Actually, selected SQL Server CE as basic for a program. It is possible to switch, but for not skilled it the automatic machine costs. Selected as least  for EF for which of a box all works (for SQLite it is necessary to create manually tables, and it to me is not pleasant). EF does not support SQL CE, as far as I know, you most likely are mistaken. It also is not necessary anywhere the automatic machine, AFAIK. You are exact it do not confuse to something another? Simply file there is no place to undertake there to second time delays, in the same place. And generally now SQL CE looks approximately same dead as . It precisely is necessary to you, to drag it in a new product? And here for SQLITE just EF works, and it is officially supported. Manually to create tables not mandatory.

4

Re: SQL Server CE - how to understand where a problem?

Hello, VladCore, you wrote: VC> I do not know what at you , but you do not check - in SQLite even migrations are supported. Enough in designer Configuration to specify VC> VC> public Configuration () VC> {VC> SetSqlGenerator ("System. Data. SQLite", new SQLiteMigrationSqlGenerator ()); VC>} VC> And where it to take? At me does not see SQLiteMigrationSqlGenerator. Packets are connected: <package id = "System. Data. SQLite" version = "1.0.105.2" targetFramework = "net45"/> <package id = "System. Data. SQLite. Core" version = "1.0.105.2" targetFramework = "net45"/> <package id = "System. Data. SQLite. EF6" version = "1.0.105.2" targetFramework = "net45"/> <package id = "System. Data. SQLite. Linq" version = "1.0.105.2" targetFramework = "net45"/>

5

Re: SQL Server CE - how to understand where a problem?

Hello, bnk, you wrote: bnk> EF does not support SQL CE, as far as I know, you most likely are mistaken. It also is not necessary anywhere the automatic machine, AFAIK. Supports completely, including migrations. It is enough to connect a packet: <package id = "Microsoft. SqlServer. Compact" version = "4.0.8876.1" targetFramework = "net45"/> bnk> you are exact it do not confuse to something another? Simply file there is no place to undertake there to second time delays, in the same place. MS always finds where to take second time delays even if it simply file And on my computer of time delays is not present. On others is. How to understand why is not present at me bnk> And generally now SQL CE looks approximately same dead as . But it works. bnk> and here for SQLITE just EF works, and it is officially supported. bnk> manually to create tables not mandatory. Here write: Unlike MS a SQL Server, as default, the free Sqlite driver from system.data.sqlite does not support Migration. So you cannot create a new database from code. You have to manually create it. https://stackoverflow.com/questions/392 … -in-sqlite

6

Re: SQL Server CE - how to understand where a problem?

Hello, Shmj, you wrote: S> In what there can be a splinter? As though it is better to find? Found out a problem. There is by the developer machine I did  EF by means of a command: %WINDIR %\Microsoft.NET\Framework64\v4.0.30319\ngen install EntityFramework.dll And on the remaining did not do. Here in it and the splinter was...

7

Re: SQL Server CE - how to understand where a problem?

Hello, Shmj, you wrote: bnk>> EF does not support SQL CE, as far as I know, you most likely are mistaken. It also is not necessary anywhere the automatic machine, AFAIK. S> Supports completely, including migrations. It is enough to connect a packet: S> <package id = "Microsoft. SqlServer. Compact" version = "4.0.8876.1" targetFramework = "net45"/> it is 2012. Since then he unfortunately had time to die a little bit. S> Unlike MS a SQL Server, as default, the free Sqlite driver from system.data.sqlite does not support Migration. So you cannot create a new database from code. You have to manually create it. S> https://stackoverflow.com/questions/392 … -in-sqlite Too the out-of-date information. "Official" (out-of-the-box) providers from M $ for EF7 (which became now Core) exactly three three: a SQL SERVER, SQLITE, In-Memory. https://github.com/aspnet/EntityFrameworkCore

8

Re: SQL Server CE - how to understand where a problem?

Hello, bnk, you wrote: S>> Supports completely, including migrations. It is enough to connect a packet: S>> <package id = "Microsoft. SqlServer. Compact" version = "4.0.8876.1" targetFramework = "net45"/> bnk> it is 2012. Since then he unfortunately had time to die a little bit. Do not try to keep up with a mode, it is not always reasonable. If the decision works - means it it is possible to use. bnk> too the out-of-date information. bnk> "official" (out-of-the-box) providers from M $ for EF7 (which became now Core) exactly three three: a SQL SERVER, SQLITE, In-Memory. bnk> https://github.com/aspnet/EntityFrameworkCore And now compare classical EF, which on 2 place in nuget-packages and 34 million downloadings and this subquality work. And as possibilities - classical EF supports both MySQL and Postgre... You hasten. MS much that tries but a little that turns out. Here phones wanted to do. Well and where these phones now?

9

Re: SQL Server CE - how to understand where a problem?

10

Re: SQL Server CE - how to understand where a problem?

Hello, Shmj, you wrote: S> And now compare classical EF, which on 2 place in nuget-packages and 34 million downloadings and this subquality work. EF turnes on a wizard in any created project even if anybody about it does not ask. Therefore at it such amount of downloadings. After the project is generated and with it were played, it either delete, or delete from it EF.