It was incredibly annoying to wait for Noname to scan the files on the hidden server. Bored with waiting, I began trawling a local Wonderland network to see if I could learn anything new.

The first five to ten pages that I looked at was just mindless drivel. A few articles about resource gathering in Wonderland, a political one describing the importance of resistance, a pity story about a family where she was a resistance fighter and he decided to work for the machines. (In the end, she accidentally shot him.) Getting discouraged, I started clicking through faster and faster.

Click, click, click, wait - go back! On one of the pages, a bold headline that said "Learn About Mind-Reading Chips" attracted my attention. Without hesitation, I followed it.

The article began by describing newly discovered chips that the resistance managed to steal from machines and which they hoped to one day reproduce. The chips were first found embedded into former human prisoners' heads and acted to connect humans to humans and humans to ... machines. The first type of connection was described in all possible aspects: for instance, a mother could connect with her child to know in-depth how he or she felt. In other scenarios, couples connected via one of these chips were discovering something new in their relationships; they called it "integrated emotional binding." The second type of connection, between humans and machines, was scarcely explained at all. It seemed a bit shady that this article would omit the part where enemies were forced to be mentally in sync with one another. Why omit the part that we were all fighting to prevent? Aren't there enough secrets in this place already?

I wondered if there was a history available for this page. Fortunately, there 

 a log of all changes to this article for the last 5 years. There was quite a bit of material, but the most significant change appeared to have happened the day before I first arrived at Wonderland. It was titled "Final cleanup." I opened it, eager to catch every word.

Of course, I should have known that getting any useful information wouldn't be that easy. There was protection on the change log. It required knowing something, called " 

 ." The only thing left to do was to search for that term in the system and learn enough to get access to the change log. The timing of the massive change couldn't be a coincidence, and I had a gut feeling something important was hiding in there.

is a mechanism of basing an object or class upon another object or class, retaining similar implementation. Inheritance allows you to re-use functionality that is already implemented in another class, and also to add custom logic on top of it. 

This class really is as simple as it looks. It prints a pet's name to the console when you call the 

 method. Now, let's imagine that your customer made a new request - to create a class specifically for a pet cat. It should have the same method, PrintName, as well as an additional one, PrintBreed, which prints the cat's breed. To solve this, you could create such a class as follows:

If you look closer, you can see that the class 

 just duplicated the functionality of the class 

 . The code for the property Name and method PrintName are copied from the class Pet. This approach has a couple key disadvantages:

. When you duplicate code, you have more code in general, and you need to support 

 of it. Any change/bugfix that needs to be implemented must be added in 

. A new programmer in your team would have a harder time understanding the structure of the project and dependencies if there is a lot of duplicate code.

 . The following is an example of what the code looks like if the class is 

When you re-use the functionality of one class in another one by using inheritance, you are 

The class whose members are inherited is called the 

 , and the class that inherits those members is called the 

 . A derived class can have only one direct base class. 

To derive class A from class B, use a colon (:) after the class A name, and then append the name for class B.

You can treat it as a copy of the code from the class B to class A.

 . Having done that, we can now use the property 

there is no code duplication when you use inheritance

Conceptually, the connection between classes that are represented by inheritance can be thought of as an 

 a specialization of the base class. In our example: a cat 

 . Beginners often wonder when one class should or should not derive from another one. A good check would be to apply the "is" rule. If one of them "is" another, you can apply inheritance, otherwise - don't. Here are some more examples: 

 . This is the proper usage of inheritance: a minivan

 . This is NOT a proper usage of inheritance. A student 

When writing code, always check whether inheritance makes sense in the current context with the is rule.

it is NOT possible to derive a class from more than one class 

Noname was taking so long that I fell asleep while trying to commit all the vageries of inheritance to memory. If you have any trouble sleeping, I can heartily confirm that reading about inheritance in OOP for twenty minutes will do the trick. You are welcome!

This lesson covers the advanced concepts of Inheritance in C#: explanation of code duplication, base class and child class, transitive nature of inheritance. All with examples, rules, and practical tasks.