Re: [Firebird-net-provider] Entity Framework 5

2017-01-25 Thread Jiří Činčura
OK, looks like this is not a problem, so I created DNET-732 for it and it will eventually happen. -- Mgr. Jiří Činčura Independent IT Specialist On Tue, Jan 10, 2017, at 18:27, Jiří Činčura wrote: > > Too much effort? > > Correct. > > Currently MS's story is only EF6 and EFCore so I don't wan

Re: [Firebird-net-provider] Entity Framework 5

2017-01-10 Thread Jiří Činčura
> Too much effort? Correct. Currently MS's story is only EF6 and EFCore so I don't want to waste too much of my free time on anything extra. Considering the move to EF6 from EF5 is not that difficult I don't see much reasons to keep it (and there has been plenty of time to do it). And of course

Re: [Firebird-net-provider] Entity Framework 5

2017-01-10 Thread Геннадий Забула
Too much effort? On 10 January 2017 at 19:21, Jiří Činčura wrote: >> Have you considered supporting two separate libraries? In two separate >> branches/nuget and so on? > > Not really. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > >

Re: [Firebird-net-provider] Entity Framework 5

2017-01-10 Thread Jiří Činčura
> Have you considered supporting two separate libraries? In two separate > branches/nuget and so on? Not really. -- Mgr. Jiří Činčura Independent IT Specialist -- Developer Access Program for Intel Xeon Phi Processors

Re: [Firebird-net-provider] Entity Framework 5

2017-01-10 Thread Геннадий Забула
Have you considered supporting two separate libraries? In two separate branches/nuget and so on? On 9 January 2017 at 16:55, Jiří Činčura wrote: > Hi *, > > anybody still using EF5 (or even EF4)? Or is everybody on EF6... > Thinking about slimming the FirebirdSql.Data.FirebirdClient and removing

[Firebird-net-provider] Entity Framework 5

2017-01-09 Thread Jiří Činčura
Hi *, anybody still using EF5 (or even EF4)? Or is everybody on EF6... Thinking about slimming the FirebirdSql.Data.FirebirdClient and removing the old EF support and keeping only EF6 (EntityFramework.Firebird). -- Mgr. Jiří Činčura Independent IT Specialist

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-30 Thread Sibylle Koczian
Am 28.09.2012 15:01, schrieb Jiri Cincura: > Use null as initializer. > Thank you, that works. But it means that I can neither create nor change my database schema from the application. Only "code first with an existing database" is possible, right? Not really a problem, but I'd like to know for

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-28 Thread Jiri Cincura
Use null as initializer. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-28 Thread Sibylle Koczian
You have Migrations turned on, but Migrations are/is not supported (currently).How can I turn off Migrations? I don't want them for the moment. I would have thought using a Database Initializer derived from DropCreateDatabaseIfModelChanges<> would turn them off, because that seems incompatible with

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-27 Thread Jiri Cincura
You have Migrations turned on, but Migrations are/is not supported (currently). -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -- Everyone hates slow websites. So do we.

[Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-27 Thread Sibylle Koczian
Hello,I'm trying to create a Firebird database in a small test application using Entity Framework 5 with Code First, but it doesn't work.Versions of everything:Windows 7 Home Premium, 64 bitFirebird 2.5.1Firebird net provider 2.7.7 (installed in the GAC, correct entries in machine.config)Visual Stu