C# Documentation: A Start to Finish Guide
If you’re a regular reader of this blog, you’ll know that?code documentation is a topic we tend to cover with a certain frequency. Another common topic is concepts related to the C# language. In today’s post, we make these two common subjects converge, by presenting a guide on C# documentation.
We’ll show you a step-by-step guide that will walk you through the necessary steps you need to take to create documentation for your C# code. You’ll start by adding documentation to your code using special XML comments and end by seeing how to generate rich documentation created from these comments. You’ll learn about the importance of code documentation, see how Visual Studio can turn the documentation you create into useful help messages, and get to know some tools that can help you in this work. Let’s get started!
As the title of the article makes clear, this post is a gentle introduction to the concept of inheritance. It’s aimed at beginners that still haven’t mastered inheritance. That means that, despite being a complete introduction, we’ll not venture into more advanced aspects of the concept. By the end of the post, you’ll not know everything there is to know about C# inheritance. Instead, you’ll have a solid working knowledge, upon which you can keep building more and more.
A good code review can feel like magic. A skilled code reviewer will deftly work through each part of a pull request, noting potential problems and proposing elegant solutions. If you’re like many developers, you recognize a good code review when you see one. You’ve probably even created a few yourself. But you’re probably also a bit unsure as to how to make sure that your code reviews are good every time.
“Everything automatable will eventually be automated.” Have you heard that saying? I’d prefer to tweak it a little bit and say that everything automatable should be automated. If you’re a regular reader of the SubMain blog, you’ll know that 
We’ve already covered so many C# concepts, and most of them relate to objects. This is hardly surprising, C# being an object-oriented language. What is surprising is that, up until this point, we haven’t covered the “thing” responsible for creating objects!
C# is about objects, 
If you’re a software developer, then I’d bet you use some kind of automated testing. And if you don’t, you certainly should. But what about “automated documentation?” Do you know what this means? Are you putting this technique to work for you? Most likely you’re not. And if that’s the case, you’ve come to the right place.
If you’re a regular reader of the SubMain blog, you’ll know that we often publish posts about fundamental concepts of the C# language. Today’s post adds yet another chapter to this ongoing series. The topic we’ll cover is, in fact, as fundamental as it can get: C# data types.
When you’re coding by yourself, for yourself, your code style doesn’t matter that much. Developers the world over have GitHub profiles full of horrible, ugly code they wrote to tinker with some new library or language. Their goal wasn’t to write pretty code, it was to learn something new. That changes when you’re working in a software team, though. Now you need to make sure not only that your code is functional, but that it adheres to team standards.
You’re a little ways into your first programming job, and things are getting easier. At first, all the code you had to deal with might have overwhelmed and confused you, but you’re starting to get the hang of it. That’s great! Now you’re wondering how to take the code you write to the next level. While there are lots of things to learn about your programming stack, many of which will make you a better programmer, there are a few that will serve you no matter what stack you work in. One of those is code documentation.