Which book to choose for an in-depth study of C#?

Question

Books

Good day. About 8-10 months ago I started learning C#, based on Herbert Schildt's book C# 4.0. The Complete Guide . A month ago, I read it in full and, to consolidate the material, ran through the book C# 6.0. The Pocket Guide by Albahari.
Right now I'm looking for the next book to learn C#. After reading reviews of different authors and books, I chose the following:

• C# 6.0. Directory. Complete description of the language (Albahari)
  
• C# for professionals. Subtleties of programming (Skit)
  
• CLR via C# (Richter)
  

I would like to hear feedback on the above books, what impression did you have after reading any of these books, what are the advantages and disadvantages of the book, and your opinion about other literature that you read and were satisfied (or upset) with the presentation is also interesting material.

Answer 1

These are all great books.
Skeet shows how the C# language developed, what its developers thought about. This gives a very complete picture.
Albahari is one of the best choices if you need to deal with some issue here and now. Almost all topics covered. Naturally, somewhere there may not be enough depth, but everything is clear and practical.
Richter is a classic. Where Albahari lacks depth, Richter will provide it. Great for "light" reading before bed, when you just want to understand something for yourself.

Answer 2

Be sure to add to your reading list "Principles, Patterns, and Techniques for Agile Development in C#" ISBN 978-5-93286-197-4, 978-0-13-185725-4 . Learn how to use language tools. And how NOT to.

Answer 3

Schildt read and upset.

Answer 4

I'm currently reading all of these books, great selection.

Answer 5

I have read the book by Jeffrey Richter, CLR via C#, Fourth Edition. I read it in English from cover to cover. At the same time, I am new to C#, but I already read something before Richter.
General impression: Jeffrey Richter is a scoundrel and a scoundrel (because he steals readers' time). He writes disgustingly. His book is really a "developer's bible" - but, unfortunately, in the truest sense of the word, because it contains information like:

I am the vine and you are the branches; whoever abides in Me and I in him bears much fruit; for without Me you can do nothing.
Whoever does not abide in Me will be cast out like a branch and wither; and such branches are collected and thrown into the fire, and they are burned.
where were you when I laid the foundations of the earth? Tell me if you know.
at the general rejoicing of the morning stars, when all the sons of God shouted for joy?
To this he said, Behold, I see four unbound men walking in the midst of the fire, and there is no harm to them; and the appearance of the fourth is like a son of God.

And so - almost the entire book - only in English. Richter has a unique talent to confuse simple and understandable things out of the blue. At the same time, he often speaks only in such a way that it cannot be clearly understood. He has a pathological desire to suck imaginary difficulties out of his finger where they do not exist.
He likes to give code examples necessarily in the form of kilometer-long sheets - in order to "drown" the necessary 2-3 (explained) lines of code in the abyss (absolutely unnecessary here, but at the same time quite complicated) long code.
Richter is a man who should be banned by law from writing books. Sheer mediocrity in terms of the ability to explain something. He himself, no doubt, knows something - but avoids the responsibility to explain it properly - because of his cowardice, I think.
Everyone who praises him - most likely, simply did not read it to the end. And I have read. The last section (multithreading) is generally almost unreadable.
Throughout the book there is unnecessary verbosity, fogging out of the blue. This person clearly has mental problems - he can only endlessly "walk around to about", but is unable to "take the bull by the horns".
His book is pretty much just rubbish - a waste of time and money. It's time, finally, to admit it - instead of our endless kowtowing before the West. Reading his book, I constantly felt a burning desire to hit him on the head with a stick. Now, unfortunately, I will have to read something else - with a normal (at least) explanation. I'm just furious about this book. There is not the slightest doubt that all this material was no problem to explain in much simpler and clearer language. The entire section of multithreading, by and large, passed completely by, it was not possible to understand anything practical there. Yes, how is it? I would understand if at least some places remained incomprehensible - but not the whole section of the book as a whole?
And it doesn't matter, I'm new to C#. The important thing is that I have read many other correct books before, and I know how to write them. This author "says a lot, but in a way that ends up saying nothing."