Entity Framework v4 support
---
Key: DNET-308
URL: http://tracker.firebirdsql.org/browse/DNET-308
Project: .NET Data provider
Issue Type: Task
Components: ADO.NET Provider, Entity Framework support
Hi *,
I'm going to convert solution/project files of NETProvider into VS2010
format next week. Has anybody problem with it?
The sources will still be buildable for .NET 2.0 and .NET 3.5. I'll
also add a new configuration into solution for .NET 3.5 build.
--
Jiri {x2} Cincura (CTO x2develop.com)
On Sat, Apr 10, 2010 at 9:53 AM, Jiri Cincura wrote:
> I'm going to convert solution/project files of NETProvider into VS2010
> format next week. Has anybody problem with it?
No problem here.
Out of curiosity, why are you going to switch to VS2010 right away?
Regards,
--
Douglas Tosi
www.sinat
Because it is 2010 times better as 2008?
Kind regards
Alexander
-Original Message-
From: Douglas Tosi [mailto:dougla...@gmail.com]
Sent: zaterdag 10 april 2010 19:34
To: For users and developers of the Firebird .NET providers
Subject: Re: [Firebird-net-provider] VS2010 solution/projec
On Sat, Apr 10, 2010 at 19:33, Douglas Tosi wrote:
> why are you going to switch to VS2010 right away
I'm using it for my daily development for about a half year, mainly
because in my company we started project based on EFv4 and ASP.NET
MVC.
For NETProvider, because of (ADO).NET 4 (and EFv4). Pr
On Sat, Apr 10, 2010 at 21:11, Alexander Muylaert
wrote:
> Because it is 2010 times better as 2008?
I don't wanna to open a flame here, but ;)
I generally agree, that it's in most points better, though that's
because it's new not 2yrs old. In fact I'm more and more using just
the editor (so
Hi Jiri
I just discover something weird in FB RC2. I posted it on tracker, but
maybe you might be able to solve (workaround) it?
Could you have a quick look at this? Maybe I'm just plain wrong.
http://tracker.firebirdsql.org/browse/CORE-2963
Thanks
Alexander
---
Hi Jiri
Dmitry responded, it seems to be a bug that is in the fb engine since 2.0.1.
It was reported early in 2007. I don't think it is the core team's highest
priority. Since they expect you to write proper sql anyway, with inners
first and then the outers.
I was thinking...
Maybe we can reord
