Light on theory and long on practical application, “Mono: A Developer’s Notebook” book bypasses the talk and theory, and jumps right into Mono 1.0. Here is a PDF sample chapter of the newly released Mono book (we will have a review in a couple of weeks).
This is good. But if you want to make Mono more popular, you have to provide free complete tutorial online or something like e-book just like Sun did:
http://java.sun.com/docs/books/tutorial/
1.0 has only recently been released. I’m sure that given a little time a wealth of tutorials will start to appear.
The book looks great, a nice refreshing design.
But if Mono is the implementation of .Net, why not just buy a book on .Net?
Indeed, the free handbook in Monodoc and on the site is still not accurate or complete! And this notebook from O’reilly is too short to spend money on IMHO (I’d wait for the ‘the complete Mono reference’ or something like that).
But if Mono is the implementation of .Net, why not just buy a book on .Net?
Yes, Mono implements System.* et al, but the Mono.* and other libraries (ByteFX for e.g.) are not included in Microsoft’s .Net
“Yes, Mono implements System.* et al, but the Mono.* and other libraries (ByteFX for e.g.) are not included in Microsoft’s .Net”
So that opens the door for a “Portable .Net” book then ….
Is it just me or are the classes being used to read/write files totally different from the ones used under MS.Net?
Is it just me or are the classes being used to read/write files totally different from the ones used under MS.Net?,
System.IO is a MS.Net namespace. All examples in the chapter use namespaces in System, except the Mono specific namespaces, for e.g. Mono.Posix
I received this book yesterday by mail and it really kicks ass. I doesn’t go really deep on C# or Gtk# but it gets you on track very fast. Great work by Ed & Niel and a great new O’Reilly concept!
This is good. But if you want to make Mono more popular, you have to provide free complete tutorial online or something like e-book just like Sun did.
Well, duh. Because this book comes from O’Reilly and from not Ximian/Novell. O’Reilly is commercial publisher.
i’ve had little to no issues with mono as of yet (coming from a long .net background), however, i am quite surprised that they would ship v 1.0 w/ such sparse documentation. a major release (especially the first one) usually implies documentation along with the bits. i know they were in a rush to get it out the door, but IMO that’s no excuse. overall, i’m quite pleased with mono though.
This chapter is a good advertising for the book.
It shows an interesting style, and seems very to the point.
I will try to get one.
I bought “C# in a Nutshell”, and I was quite impressed with how easy the book was to read . I’d definitely recommend it to anyone who’s planning on doing cross-platform development with Mono/.Net. Looks like I’ll be up this book, too…
-Erwos
>This is good. But if you want to make Mono more popular, you >have to provide free complete tutorial online or something >like e-book just like Sun did.
The book is pretty cheap as it is, why must everything be ‘free’? Someone put a lot of work into writting this book, I see no problem in them charging the small amount they do.
OK, sorry… this is a little OT, but I gotta ask:
(coming from a long .net background)
how can anyone come from a “long .NET background” when .NET is so new? or did you help write it?
The betas were out a couple of years ago, so yes its possible to have a long .net background.
i’ve been writing software targeting .Net since beta 1 (circa summer of 2000). the company i was with began writing production software as of beta 2 (circa early 2001) i have been writing nothing but .Net code since. .Net is anything but new, and i know of at least a few fortune 100 companies who were writing production software as of beta 2. 4 years isn’t long by some standards, but by computer standards it’s almost ancient. get yer facts straight.
“production software as of beta 2”
Why does that and the fact that your domain is bankofamerica.com worry me so much…
Bank of America was gunna go under the litigous knife of SCO, but somehow that decision got buried in MS Word metadata… gotta wonder what made McBride changed his mind (early .NET adoption is probably not the reason).