Schedule

Schedule

Friday, January 30

1422640800 Tech News Today
1422644400 This Week in Law
1422662400 Tech News 2Night

Saturday, January 31

1422730800 The Tech Guy

Sunday, February 1

1422817200 The Tech Guy
1422828000 This Week in Tech

Monday, February 2

1422900000 Tech News Today
1422903600 Triangulation
1422909000 iPad Today
1422921600 Tech News 2Night

Tuesday, February 3

1422986400 Tech News Today
1422990000 MacBreak Weekly
1422997200 Security Now
1423004400 Before You Buy
1423008000 Tech News 2Night
1423011600 All About Android
1423020600 Padre's Corner

Wednesday, February 4

1423067400 FLOSS Weekly
1423072800 Tech News Today
1423076400 Windows Weekly
1423083600 This Week in Google
1423094400 Tech News 2Night
1423096200 Android App Arena
1423101600 Ham Nation

Thursday, February 5

1423159200 Tech News Today
1423162800 Know How...
1423166400 Marketing Mavericks
1423171800 Coding 101
1423175400 Home Theater Geeks
1423180800 Tech News 2Night
1423182600 The Giz Wiz

Friday, February 6

1423245600 Tech News Today
1423249200 This Week in Law
1423267200 Tech News 2Night

Saturday, February 7

1423335600 The Tech Guy

Sunday, February 8

1423422000 The Tech Guy
1423436400 This Week in Tech

Most Recent Episodes

This Week in Computer Hardware

NVIDIA and the GTX 970, PCPer VLAN, and Direct X 12 in Windows 10.

The Giz Wiz
Episode #1503: RIP SkyMall January 29th, 2015

Remembering SkyMall.

Tech News 2Night

Social media announcements, Cortana predicts the Super Bowl

Know How...

Back from Daytona, G+ Feedback, and Networking.

Home Theater Geeks

Ultra High Def, the future of TV, and the alliance.

Coding 101

The philosophy of assembly.

Marketing Mavericks
Episode #40: The Big Game January 29th, 2015

The Super Bowl, social war rooms, halftime ads.

Tech News Today

Facebook reports some big numbers and more.

Ham Nation

Don Wilbanks and George Thomas show what they found at Capital City Hamfest, Jackson, Mississippi.

Android App Arena
Episode #30: Travel Apps January 28th, 2015

Skyscanner, Tripit, Hungry?, Facebook Lite

Coding 101 32

C# Abstract Classes and Interfaces

August 28 2014

Hosts: Fr. Robert Ballecer, SJ and Shannon Morse

Guest: Lou Maresca

The Code for today's show is available at our: Github

Snubs Compiled
No Viewer Submitted Code, however we did get some useful tips for C# from our community:

Cosmic Ray links us to a C# Fundamentals series that's super useful for newbies!

Nathan says learning the syntax of the languages is great, but you need to know how to problem solve!

Kelvin links us to Mono, for Mac users

Joe gives us info on how to get C# running via notepad!

Ivory Tower
Interfaces, Classes, & Abstract Classes

Remember from last week that "Classes" are blueprints
- They are a collection of Methods, variables, properties and events
- Classes DO NOT EXIST until they are created (i.e. the difference between having a blueprint and the building built from those blueprints)
- When an instance of a class is "created" -- and "object" is born

Declaring a Class
public class C101

{

//Fields, methods, properties, events
// everything in the "blue print" goes in here

}

Creating an OBJECT of a class:
C101 object1 = new C101();

** One of the topics that was covered towards the end of our "Code Warrior" section last week, was the idea of inheritance.
-- You can make new classes that inherit their members from another class, with derrivations from the original class.

Inheriting from a class
public class Module4 : C101

{

//Fields, methods, properties, events
//everything in the ""blue print"" goes in here

}

** However, there's another way to do that... another way that perhaps is MORE suited for inheritance and derrivation than a class... an ABSTRACT CLASS

Now let's talk about "Abstract Classes"
* If classes are blueprints --- things that are ready to create --- to turn into objects, then "ABSTRACT Classes" are architectural designs.
-- They have the right shape of the thing to be created
-- They have much of the information needed to create the thing being created
-- But they are not complete
-- They cannot be instantiated - (They cannot not be "created" into an object)

* The sole purpose of an abstract class is to act as a "base" for inheritance
-- They cannot be instantiated, but a derrivative class, which inherits the abstract members from the abstract class, can be.
-- That derrivative class must provide proper implementation for all the abstract members of the abstract class, then it CAN create an object. (It complete's the blueprints)

Declaring an abstract class
public abstract class C101

{

//Fields, methods, properties, events
//everything in the ""blue print goes in here

public abstract void menu()

{

}

}

Inheriting from an abstract class
public class Module4 : C101

{

public void menu()

{

Console.WriteLine("This is a Menu");

}

}

* The inherited class from C101 MUST provide implementation for any abstract members within that class.

A few things about Abstract Classes:
1. They are created with the keyword "abstract"
2. They are incomplete and therefore CANNOT be instantiated. (an object cannot be created from the class)
3. Abstract classes and incomplete, and therefore can only be used as a base class
4. Non-abstract classes that are derived from abstract classes MUST provide proper implementation for any abstract members that are inherited from the abstract class.

Why have an Abstract Class?
* Abstract classes ENFORCE a particular hierarchy - They FORCE those who are inheriting from the class to code in a particular way to complete implementation.
* Abstract classes give us "parent" classes from which we can derive objects with customized implementation
* Going back to the blueprint:
-- An abstract class can give us the overview of what an object should look like, but then each derrivative class can implement the pieces of the abstract class as then need to be to best suit function

Let's talk about an Interface
* An Interface is like an Abstract class in that it can be used to define hierarchies for any sub-classes
* Unlike an Abstract Class, an Interface has NO body.
-- It's just the definitions of methods, with no body whatsoever.

Get in Touch With Us!

* Subscribe and get Coding 101 automatically at TWiT.tv!
* Follow PadreSJ and Snubs on Twitter.
* Watch the show live and join the chatroom every Thursday at 1:30pm PST.
* Email us at Padre@twit.tv and Shannon@twit.tv.
* Join our Google+ Community!
* Check out our transcripts.