Re: [Firebird-net-provider] .NET 4

2010-01-03 Thread Kjell Rilbe
Jiri Cincura wrote: > 1. Dropping .NET 2.0 support. Could there be a .Net 2.0 branch that would be kept alive for bugfixing for a year or two, but no new features? I would assume that those who are still on 2.0 for various reasons would find it rather disappointing if 2.0 were to be dropped compl

Re: [Firebird-net-provider] .NET 4

2010-01-03 Thread Ivan Arabadzhiev
Happy new year :) Just to express a modes oppinion. 2.0 Support seems old enough to be dropped (although I am still actively using it). Sooner or later, Microsoft will forget it and there will be no other choice(like they did with the 2.0 sp2, which is not provided standalone). I haven`t read

Re: [Firebird-net-provider] .NET 4

2010-01-03 Thread André Litfin
Hello Jiri, happy new year! I think dropping 2.0 FW support isn't a good idea as we are still using only FW 2.0 for some reasons (installing FW 3.5 on client PCs without internet connection in german language isn't possible). André Litfin Xsigns GmbH & Co. KG > -Ursprüngliche Nachricht-

[Firebird-net-provider] .NET 4

2010-01-03 Thread Jiri Cincura
Hi *, as the new .NET 4 will be out soon I have couple of thoughts for further development. Feel free to express your POVs as I definitely don't know all corners where .NET provider is used. 1. Dropping .NET 2.0 support. The .NET 3.0 and mainly .NET 3.5 is just update for .NET 2.0. There's no new