ASP.NET is quite a controversial piece of the .NET framework. ADO.NET is another controversial library, that has no replacement.
As Thomas Jefferson said ... the price of freedom is eternal vigilance. Why can't we just stick with the ECMA standards and create true open-source alternatives for the rest of the .NET framework ? Is it really that hard ? I mean, besides licensing reasons, really ... ASP.NET is very tool-oriented to be bearable without VS.NET, and ADO.NET simply sucks, as I've never seen a more poorly designed database access library. I thought about starting my own database access library, similar to Python's or Perl's DBI. Shouldn't be too hard to create such interfaces and then to create a mysql adapter by wrapping the mysql C library, the only problem being the limited free time I have. Kornél Pál wrote: > Hi, > > If you don't want to use ASP.NET and/or System.Windows.Form it's up to you > but note that the fact that there is a closed source implementation of them > (i.e. Microsoft .NET Framewrok) doesn't mean that you should avoid their > open source implementations (i.e. Mono or Portable.NET, IMHO Mono is much > better:). _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
