Sounds great. I've been really looking forward to this book for a while. The first and second editions were easily the most enjoyable technical books that I have ever read.

Hopefully there will be an eBook (preferably PDF) available. O'Reilly now sells Microsoft Press books, but there is no mention of the 3rd edition yet. (Amazon only sells DRM-defective eBooks, so that is not an option.)

Awesome! I'm really looking forward to reading this new edition. Thanks for all your hard work!

m

Fantastic news! I pre-ordered this several months ago. Can't wait!

This is really a good news for us. Thanks Jeff. Well done!

PingBack from http://topsy.com/tb/bit.ly/8N60Bg

Awesome!!!! Can't wait. I pre-ordered mine last week!!!

New version of this 'cult' book ? Great news. I'm going to pre-order it.

Now I read your Windows via C/C++ 5th ed. and would like to ask you Jeff, if you are planning to write 6th edition.

When I type in Amazon serach box term 'Windows via C/C++' autocomplete feature offers me 'windows via c c++ sixth edition' searching option.

Surely I'm not the only one who is looking forward for next edition of this great series. :)

Jan.

Hi, just wondering, is there a pdf version of this book that I can buy? the reason I ask is that I use annotation tool of Acrobat to annotate my reading thought. thus I would prefer a pdf book than the printed one. thanks.

what places will sell CLR via C# 3rd Edition? amazon uk sells it for £45.99, which is absurd.

also, do you plan on making a kindle version available?

Will there be an eBook version for purchase?

The book looks great, and I look forward to replacing my 2nd Edition as soon as it's available. I do have one critique, though.

I was browsing some of your code samples, and I noticed that in some of your thread-safe code (i.e. Ch11-1-EventSet), you use the obsolete "Monitor.Enter(object obj)" method instead of using either the new "Monitor.Enter(object obj, ref bool lockTaken)" method or the C# "lock" keyword, which emits a call to the latter method when compiling against .NET 4.0. You also don't surround the synchronized code with a try/finally block.

It seems to me that if you're trying to teach developers how to write "correct" thread-safe code, you could do better with your examples.

I'm also curious as to why you implemented your event-raising extension methods in a way that requires passing the handler as a 'ref' parameter. Would the extension method below not work just as well, with just as much thread safety? I don't always catch all the nuances of thread safety, so I could certainly be missing something.

public static void Raise(
this EventHandler handler,
object sender,
TEventArgs e)
where TEventArgs : EventArgs
{
if (handler != null)
handler(sender, e);
}

Example usage:

this.MyEvent.Raise(this, EventArgs.Empty);

Awesome!!!

The new version just arrived this morning. Do you happen to have a list of sections that are new or largely updated? As with all your books I've owned throughout the years, I read the prior version of this one cover to cover and, though I fully intend to go back and re-read the whole thing, I was hoping maybe there was a way to zoom in on the new stuff right away.

Btw, the foreword by your wife was hilarious. She sounds a lot like my wife...

Cheers!
-Brian

Is it true that this is your LAST book? Don't do this...

Hello!

First off, I would like to say from one professional to another, I greatly respect and admire your work and would like to take this opportunity to thank you for the excellenct quality of your books, one of which is absolutely required reading in my line of work (C# via CLR v2/3). If I see your name attached to an article I always make it a point to read it lest I should miss something worthwhile. Again, many thanks and kudos!!

Now for the question : In the chapter 21 source-code (C# via CLR v3) regarding the WeakEventHandlerDemo, I believe I have uncovered an issue where the WeakEventHandler is cleaned up even though there's a hard-reference to the DoNotLiveJustForTheEvent instance. For example, if you run the demo as is it works as expected : clicking on the test button will invoke the event but since the event owner's instance is not hard-referenced, it will eventually be collected at which point clicking the test button will not longer fire the event. Works like a charm so far in the case where the event owner's instance is not referenced. Now let's change the code such that we keep a hard-reference to the event owner's instance (in other words keeping the instance alive indefinitely). I modify the demo code as follows :

form.Tag = new DoNotLiveJustForTheEvent(); // hard reference
btnTest.Click += new WeakEventHandler((form.Tag as DoNotLiveJustForTheEvent).Clicked) { RemoveDelegateCode = eh => btnTest.Click -= eh };

I would have expected that since there's now a hard-reference to DoNotLiveJustForTheEvent it would never get collected, but it does!

So my question is : am I missing something?

Regards,

Anthony

great! I have read 2nd edition, and look forward to 3rd ed. !
Thanks to Jeffrey!

This is an amazing book. Must for people who hopes/wants to be a good .net programmer.

It s a great book on .NET.
Thanks for your sharing,I have download it.

I'm about halfway through it now. I noticed in the forward your wife mentioned it is planned to be your last book. Hopefully this is not the case!

Thanks for making me a better programmer!

Hi Jeffrey,

Do you have any plan to update book Windows Via C/C++? 'Cause Windows is popular now.

Thanks,
Pat

Just reading CLR via C# (now on chapter 26/27). Coming from a Unix background (server-side Java developer) and having to move to C#/.NET, this book hot the spot for some 'under the hood' c# server-side developer info.

One question...any plans to bring out a WinRT C++ book in the same vein as your current C/C++ book?

C++ appears to be back in full swing on MS (...and OSX/iOS, Android, Arduino...).

Cheers,
Steve