Hello Jiri,

I think that you should not drop support for .NET 2.0. There are many
developers who are using the.NET 2.0 Firebird Provider especially in older
projects, including me.

.NET 2.0 is not old. It is mature and stable. Applications targeting .NET
2.0 can run on most of Windows XP systems, Windows Vista and Windows 7
without requiring from the end user to install a 20+MB Framework installer.
Here is an article related with this:
http://quinxy.com/2011/01/24/net-dotnet-install-base-statistics-picking-your-framework-version/

Also, Winforms cannot be considered as an old and out of date technology
because it was introduced from the .NET 1.0 back in 2002. There are many
developers who still prefer to build business apps on top of WinForms
instead of WPF and target .NET 2.0 or 3.5 and most of the projects that use
the .NET provider are Winforms projects.

Take a look at the big component vendors like infragistics, devexpress etc.
Their Winforms suites target .NET 2.0.


Regarding the .NET Compact Framework, maybe you could drop support for this,
or provide some bug fixes if there is a serious bug. It looks like the
future in the mobile devices is in iPhone/iPad, Android and maybe Windows
Phone.
If in the future there would be a native firebird build for these operating
systems it would be fine. Firebird .NET provider is already ok, because it
runs on Mono.


As a developer, I would still like to see new versions of .NET Firebird
provider targeting the .NET 2.0 for at least 2 years from now. As for the
.NET Compact Framework I am not planning to maintain or build a new project
on top of this technology.

Finally, thank you for all your efforts to build and maintain the .NET
Firebird Provider. Your hard work is appreciated from all the developers who
are using it.

2011/8/13 Jiri Cincura <disk...@cincura.net>

> Hi *,
>
> I'd like to open discussion about versions of .NET Framework we're
> going to support in 3.0+ versions of .NET provider.
>
> 1. I'm strongly thinking about dropping support for .NET 2, because a)
> it's old, b) the .NET 3.5 doesn't change CLR, just bunch of new stuff,
> c) upgrade itself is free, d) it will save some resources on
> maintenance.
>
> 2. For the Compact Framework version, I have no idea what to do with
> it. Obviously the CF is dead on mainstream with Windows Phone, but
> there's still a lot of devices with WinCE (hard to predict what MS
> will do with this part of market). The current shift is to data feeds
> etc., but who knows, maybe somebody has good reasons to have direct
> calls.
>
> Any thoughts?
>
> --
> Jiri {x2} Cincura (x2develop.com founder)
> http://blog.cincura.net/ | 
> http://www.ID3renamer.com<http://www.id3renamer.com/>
>
>
> ------------------------------------------------------------------------------
> FREE DOWNLOAD - uberSVN with Social Coding for Subversion.
> Subversion made easy with a complete admin console. Easy
> to use, easy to manage, easy to install, easy to extend.
> Get a Free download of the new open ALM Subversion platform now.
> http://p.sf.net/sfu/wandisco-dev2dev
> _______________________________________________
> Firebird-net-provider mailing list
> Firebird-net-provider@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
------------------------------------------------------------------------------
FREE DOWNLOAD - uberSVN with Social Coding for Subversion.
Subversion made easy with a complete admin console. Easy 
to use, easy to manage, easy to install, easy to extend. 
Get a Free download of the new open ALM Subversion platform now.
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Reply via email to