On Mon, Jan 4, 2010 at 11:34, Luigi Piccinni
<[email protected]> wrote:
> Programmers who uses .NET 2.0 (for example because they cannot upgrade the
> software in production from 2.0 to 3.5 or 4) have to get the provider's
> source code every new release and recompile it using VS2010 (thanks to the
> multi-framework functionality), or a specific .NET 2.0 compiler (VS2005,
> CSC2, ...)
It will not work. First because the new C# language features (like
object initializers) and second because of new .NET objects (i.e. Func
or L2O).
> I don't know how many C# programmers out there need .NET 2.0 support, and
> how many of those ones know this issue and/or how to workaround it.
> Maybe, if .NET 2.0 support shall fall, it would be better to leave a message
> on the provider's download page to explain the necessary steps to have a
> full-operative provider in .NET 2.0 environment.
>
> Or... since the solution will be switched to VS2010, the simplest way would
> be to continue releasing the libraries compiled in the different
> environments ;)
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
