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 Vista, Windows 7 and most Windows XP systems. 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 is more than 50mb and I think that this is not good. The big installer size is a reason for some users not to try a trial version of an application. Also, please take a look at this Wikipedia article, in the criticism section: http://en.wikipedia.org/wiki/.NET_Framework Also most of the big Net component vendors, like Devexpress, infragistics etc are building their windows forms components targeting NET 2.0 and supporting VS 2005/2008. They know that they will lose a huge market share if they drop support for NET 2.0 in their windows forms components. I suggest to wait some more time before dropping Net 2.0 provider support. A good time to drop net 2.0 support will be when most of the Windows XP users move to windows 7 or a newer OS, with the Net 3.5 preinstalled. Yianni 2010/1/3 Jiri Cincura <disk...@cincura.net> > 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 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 > the code more clean and probably also faster. Taking into account > limited resources project has, this will also allow focus more on new > features. > Until the official .NET 4 release there will be still support for .NET > 2.0. But not after it. > Builds for .NET 3.5 and .NET 4 will be provided on site as now. > > 2. CSC 4 will be the official compiler. > New compiler means (maybe) better code. New features and syntactic > sugars means faster development. You don't need to build provider > yourself so you are not affected by this. If you're building it > yourself you don't need VS2010 to install. Just use CSC thru > cmd/MSBuild and you're fine. > [1] > > 3. Switching the solution(s) to VS2010. > With 2. this is pretty obvious. As you're safe with us using new > compiler, this is more true for new IDE. > [1] > > What I don't know is whether there's some demand on VS2005 DDEX > support dropping and extending support for new stuff in VS2008. VS2008 > adds some really minor features, as far as I remember when checking > it, so it's probably not worth doing it. But maybe you have different > opinion. > > The development overall will be still focused on new > ADO.NET<http://ado.net/>(incl. > EF) features support as well as features in new FB engine versions. > > > [1] AFAIK the core guys have plans to switch to VS2010/C++ as official > compiler for engine too. :D > > -- > Jiri {x2} Cincura (CTO x2develop.com) > http://blog.cincura.net/ | > http://www.ID3renamer.com<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 > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider >
------------------------------------------------------------------------------ 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 Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
