OK, there doesn't seem to be any more discussion around this. And
because, as stated before, MS is not going to support 4.0 (and also 4.7
is now out for all systems), the minimum supported version in next major
version will be 4.5.2. If somebody wants the 4.0 the previous versions
are always
55
Aan: For users and developers of the Firebird .NET providers
Onderwerp: Re: [Firebird-net-provider] .NET 4 support
I am still using 4.0 due to the difficulty upgrading 500+ computers and a
painful amount of customers still on XP. The downside of desktop software.
That being said the current code is stable and
I am still using 4.0 due to the difficulty upgrading 500+ computers and a
painful amount of customers still on XP. The downside of desktop software.
That being said the current code is stable and fast in our experience so
would be happy to stay on the current version until we are ready to upgrade
Hello *,
reading the
===
As previously announced, starting January 12, 2016 Microsoft will no
longer provide security updates, technical support or hotfixes for .NET
4, 4.5, and 4.5.1 frameworks. All other framework versions, including
3.5, 4.5.2, 4.6 and 4.6.1, will be supported for the
Yes Jira, but this makes the assumption that every web host out there
currently supports 3.5 hosting, which they do not all seem to offer as
default at present. Many hosts still only offer 2.0 as standard, and
are only just starting to make migrations up to 3.5 hosting offerings.
Whislt I can
Hi,
At January-03-10, 12:20 PM, Jiri Cincura wrote:
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 runtime or changes in bases. So there's no risk installing this
update. This step will provide us option to use new features and make
On Sun, Jan 3, 2010 at 21:44, Kjell Rilbe kjell.ri...@datadia.se wrote:
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 completely. Might
be a reason to switch away from FB?
For me personally, our project is on
Jiri Cincura wrote:
On Sun, Jan 3, 2010 at 21:44, Kjell Rilbe kjell.ri...@datadia.se wrote:
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 completely. Might
be a reason to switch away from FB?
For me personally,
I build 2 applications with the installer size that is less than 16 MB.
Most of the end users have NET 2.0 installed in their OS and do not need to
download anything else.
Even if they have to download Net framework 2.0, it is around 23MB and this
is rare.
Net 2.0 applications run as-is in
2010/1/4 Γιάννης Μπουρκέλης yiannis1...@gmail.com:
Most Windows XP users do not have NET Framework 3.5 installed in their
systems, so if they want to run a net framework 3.5 application, even if
this application is only some megabytes, they will have to download the huge
net 3.5 runtime, which
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
-
Von: Jiri Cincura [mailto:disk...@cincura.net]
Gesendet: Sonntag, 3. Januar 2010 17:20
An: For users and developers of the Firebird .NET providers
Betreff: [Firebird-net-provider] .NET 4
Hi *,
as the new .NET 4 will be out soon I have couple of thoughts for
further development. Feel free
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
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
14 matches
Mail list logo
