Linked by Eugenia Loli on Thu 9th Feb 2006 22:54 UTC
Mono Project Apress' open source series of books recently unveiled Mark Mamone's "Practical Mono", a book targetting new .NET developers. We take a quick look at the book below.
Permalink for comment 94421
To read all comments associated with this story, please click here.
Member since:


well the problem with these books is: We don't need yet another book describing C# and .NET.

What we need is a book describing gtk#, glade#, gnome#, gconf#, dbus#, gecko# and so on.

There is no good tutorial about dbus#. And I wanna have more documentation about these Unix/Linux-specific technologies. I would also buy a book, if it would describe these technologies.

But currently Mono does not support .NET 2.0 completely and the APIs of dbus are still changing very often. So this is not the time for books about mono only, but later hopefully.

I suppose the book will primarily use .NET 1.0, because of the missing features of .NET 2.0 in mono. But .NET 2.0 is, what is interesting.

For everything else I can buy any other .NET 2.0 book.

But another question: In Java development we have a lot of standards and long release cycles. Java 1.4 has been the newest version for a long time. And we have standards j2ee, that don't change very often.

My fear about mono is, that Microsoft will change the technology very often. .NET 2.0 has been released a few month ago, Microsoft is already working on .NET 3.0. Don't know, when it will be released, but Mono will have .NET 2.0 in the end of 2006 completely implemented. Maybe a few month, or 1 year later .NET 3.0 (C# 3.0) will be released and Mono can't follow this speed.

Or is this wrong? Well as developer I don't wanna learn every 2 years everything completely new. Mono really looks nice and I like it. But I don't wanna learn it now and learn it in 4 years completely again.

I have learned Java 3 years ago and my skills are still useful and my programs in Java 1.4 are still runnable in Java 1.5. I hope this will be similar with .NET too. The step .NET 1.x to 2.0 caused a lot of broken apps.



Reply Score: 5