#4 in Microsoft NET books
Use arrows to jump to the previous/next product

Reddit mentions of CLR via C# (Developer Reference)

Sentiment score: 5
Reddit mentions: 7

We found 7 Reddit mentions of CLR via C# (Developer Reference). Here are the top ones.

CLR via C# (Developer Reference)
Buying options
View on Amazon.com
or
    Features:
  • Use with SIP Service ONLY - Does Not Support Google Voice
  • Make free calls on the OBiTALK Network - Connect to other OBi Devices
  • Some of the OBi110 Calling Features: Call Forward, Caller ID – Name - Number, Anonymous Caller Blocking, Message Waiting Indication - Visual and Tone Based
  • Manage Your OBi, Connect to Your Friends' OBi Devices, Add Services, Speed Dial Up to 99 OBi Endpoints or Phone Numbers
Specs:
Height9 Inches
Length7.38 Inches
Number of items1
Weight2.7998707274 Pounds
Width1.5 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 7 comments on CLR via C# (Developer Reference):

u/CSMastermind · 4 pointsr/learnprogramming

I'd suggest you should pursue software development as a career path. Once you're working full time as a developer it will be much easier for you to move into a .NET role if you choose.

The career market can be hit or miss. There are plenty of jobs using those technologies but they're less ubiquitous than say Node or Java.

In terms of keeping up your skill, Pluralsight has some amazing content. And I'd recommend these books:

Design Patterns in C# - probably the first book I'd read.

CLR via C# - In-depth, targeted at professional developers, and absolutely crucial for anyone doing it professionally.

Agile Principles, Patterns, and Practices in C# - Will help get ready to work on a professional software development team with a slant towards Cc#.

Pragmatic Unit Testing in C# with NUnit - Also important for working as a professional C# developer.

More Effective C# - Is more of a specialist read. Might be helpful after you've worked for a year or two.

Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries - Is better suited for a technical lead or architect. But could be useful to keep in your back pocket.

u/Poloniculmov · 2 pointsr/Romania

wiki zice ca Zamiatin ar fi o influenta pt Ursula Le Guin, trebuie sa incerc.

Din cartile de IT e ceva bun? Eu am recitit de curand CLR via C# si o ultra recomand oricui scrie C#.

u/ZeroBugBounce · 1 pointr/learnprogramming

CLR via C# might be a good segue for you after you get over the initial "this is different" feeling of C#. It's comprehensive, deep and Jeffrey Richter is an old-school Windows/C++ guy (he also writes Windows via C/C++) so I get the feeling he makes C++ people feel comfortable when he talks about .NET.

u/myevillaugh · 1 pointr/learnprogramming

Programming C# 4.0 is great for learning and starting out.

Once you're comfortable with the language, go through CLR via C#. This will teach you how things work in detail.

u/drmcclassy · 1 pointr/EngineeringStudents

For anyone getting into programming, I strongly recommend The Pragmatic Programmer

This is a little more specific, but if anyone is working with .Net, I'm currently reading CLR Via C# and I think it's amazing.

u/[deleted] · 1 pointr/csharp

You would do well to invest in a copy a copy of CLR via C# by Jeffrey Richter. It's a great book that will answer this question, and a tonne of others in great detail.

u/zachary12 · -1 pointsr/learnprogramming

Not much help re: which language. Logic would dictate the next move to be language agnostic design patterns, re-factoring et alli. <- ignore, did not read.

For a decent C# book, I'd recommend CLR via C# (http://www.amazon.com/CLR-via-C-Jeffrey-Richter/dp/0735627045)/