What book would you recommend to learn C# from 0?
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
Always read the spec. Anything else is wrong.
-
Always read the spec. Anything else is wrong.
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
.NET Book Zero[^], without a doubt! /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Yes you can - but not everyone else will, so you get a lot of lazy coders using
varall the time for example and to hell with the poor sod who has to maintain it in six months time!Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
:) Of all the useless things that have been added to the language over the years, var isn't one of them. I've long been opposed to var myself, but these days, when I see I've used var in some of my older code, it generally means the exact type didn't matter to me back then, and it still shouldn't matter to me today. Some will abuse it for sure. But it's got its use.
-
.NET Book Zero[^], without a doubt! /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Ravi Bhavnani wrote:
.NET Book Zero[^], without a doubt!
Agree 100%! Also, get LINQPad (free at LINQPad - The .NET Programmer's Playground[^]) It's a fantastic tool for writing snippets or entire programs. Great for use with dotNet Book Zero too.
-
:) Of all the useless things that have been added to the language over the years, var isn't one of them. I've long been opposed to var myself, but these days, when I see I've used var in some of my older code, it generally means the exact type didn't matter to me back then, and it still shouldn't matter to me today. Some will abuse it for sure. But it's got its use.
It has it's uses - you can;t do Linq without it - but when you get lazy f'wits using it on every variable definition it's a PITA for maintenance:
var i = 666;
Is just lazy.
var p = ComplicatedFunctionInAnotherClass(long, list, of, parameters);
Is lazy, stupid, and uncaring of maintenance or the poor sod who will have to do it.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
Programming in the key of C# by Charles Petzold is excellent, especially when coming from older C-family languages
-
It has it's uses - you can;t do Linq without it - but when you get lazy f'wits using it on every variable definition it's a PITA for maintenance:
var i = 666;
Is just lazy.
var p = ComplicatedFunctionInAnotherClass(long, list, of, parameters);
Is lazy, stupid, and uncaring of maintenance or the poor sod who will have to do it.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
OriginalGriff wrote:
t has it's uses - you can;t do Linq without it
Linq is itself too often used/abused when often it's really not necessary at all, it's backward syntax order is a PITA for those of us that work in multiple languages and later need to unravel some newbies 'I can do it all in one line' compound statements. I'd not loose a second sleep if it were removed entirely.
signature upgrading ... please wait.
-
OriginalGriff wrote:
t has it's uses - you can;t do Linq without it
Linq is itself too often used/abused when often it's really not necessary at all, it's backward syntax order is a PITA for those of us that work in multiple languages and later need to unravel some newbies 'I can do it all in one line' compound statements. I'd not loose a second sleep if it were removed entirely.
signature upgrading ... please wait.
I completely agree on the syntax - that's why I use the methods instead - but Linq does have some advantages over the "loads of loops" approach! :-D
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
I know this is not exactly an answer to your question, but I would warmly recommend the following: 1) Job interview questions as by far the best source of condensed information about very handy C# features. A 100 questions interview is worth 314 pages in a book. 2) F..k Occam's razor. Complicate! Go to Stack Exchange and check three solutions to your problem, even if you know how to solve it. It helps build your skills beyond trivial. 3) Twitter for practicing code optimization.
-
Can't recommend that book enough.
Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
If you want something that starts at the core of C# and - to a degree - programming, I'll have to recommend Rob Miles' Yellow Book[^]. It certainly helped me learn C# quite thoroughly, although I'll have to admit that he was one of my lecturers when I attended university.
-
I'd disagree to an extent: they ripped C++ to bits when they first created C# and got rid of a lot of the "dangerous" stuff - memory leak causes and so on - to create a simpler language that was faster to develop with than native C++ as a result. Since then, they have been layering on more complexity - some of it useful and justified, some of it badly abused. It's perhaps getting to the point where C# needs to be ripped apart and the same exercise done again (.NET Core would have been a good opportunity to do this)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
OriginalGriff wrote:
C# needs to be ripped apart and the same exercise done again
Couldn't agree more. It's getting so bloated and ugly that it's starting to look like C++.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
I'd also agree on "C# in a Nutshell" by Joseph and Ben Albahari. If you ever really want to take a deep dive into C# and the CLR I highly recommend "CLR via C#" by Jeffrey Richter. In the meantime though, the Microsoft Docs on C#[^] are quite good to start off with :thumbsup:
Jon McKee wrote:
"CLR via C#"
This book is awesome. Must read for an in depth understanding of C# on top of .net.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
It has it's uses - you can;t do Linq without it - but when you get lazy f'wits using it on every variable definition it's a PITA for maintenance:
var i = 666;
Is just lazy.
var p = ComplicatedFunctionInAnotherClass(long, list, of, parameters);
Is lazy, stupid, and uncaring of maintenance or the poor sod who will have to do it.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
I agree with using a var for what clearly should be an int. Or should it be a long? Or a 64-bit unsigned int? As for your 'p' example--it all depends on what you do with it next. If you just need to hang on to it so you can eventually return it from the current function, or to pass it as a param to another function, then under those circumstances I'd say the exact type shouldn't matter to a reader.
-
I completely agree on the syntax - that's why I use the methods instead - but Linq does have some advantages over the "loads of loops" approach! :-D
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
Agreed! Linq makes things easier to write, easier to maintain, easier to understand, and just makes code 'prettier'. I cannot stand ugly code!
-
Pro C# 6.0 and the .NET 4.6 Platform[^] by Andrew Troelsen. I've not read this edition (I have the VS2008 version), but it was a very good introduction.
Software Zen:
delete this;I agree Troelsen's book is very good BUT as a former instructor NOTHING beats a textbook with structured lessons. Deitel and Deitel are arguably the best textbook publishers and "C# A Programmer's Introduction" is what I would recommend to get started from scratch. Expensive but worth it if you are disciplined enough to do every excercise as if you were in school else a waste of money that will end up on the shelf next to Troelsen's "C# and the .NET Platform."
Clinton Gallagher
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
This one helped me get off the ground https://www.murach.com/shop/murach-s-c-2015-detail
-
Hi all, Coming from Visual C++. I'll have a little bit of time in a while and I'd love learning C#... Which book would you recommend me? Thank you! :thumbsup:
