Schedule

Schedule

Thursday, October 30

1414711800 The Giz Wiz

Friday, October 31

1414774800 Tech News Today
1414778400 This Week in Law
1414785600 Android App Arena
1414796400 Tech News 2Night

Saturday, November 1

1414864800 The Tech Guy

Sunday, November 2

1414954800 The Tech Guy
1414969200 This Week in Tech

Monday, November 3

1415037600 Tech News Today
1415041200 Triangulation
1415046600 iPad Today
1415059200 Tech News 2Night

Tuesday, November 4

1415124000 Tech News Today
1415127600 MacBreak Weekly
1415134800 Security Now
1415142000 Before You Buy
1415145600 Tech News 2Night
1415149200 All About Android
1415158200 Padre's Corner

Wednesday, November 5

1415205000 FLOSS Weekly
1415210400 Tech News Today
1415214000 Windows Weekly
1415221200 This Week in Google
1415232000 Tech News 2Night
1415239200 Ham Nation

Thursday, November 6

1415296800 Tech News Today
1415300400 Know How...
1415304000 Marketing Mavericks
1415309400 Coding 101
1415313000 Home Theater Geeks
1415318400 Tech News 2Night
1415320200 The Giz Wiz

Friday, November 7

1415383200 Tech News Today
1415386800 This Week in Law
1415394000 Android App Arena
1415404800 Tech News 2Night

Saturday, November 8

1415473200 The Tech Guy

Sunday, November 9

1415559600 The Tech Guy

Most Recent Episodes

Coding 101
Episode #41: Mark Smith October 30th, 2014

Speaking with "Smitty", master of the microcontroller.

Know How...

Project Loon 2.0, Quad Motors & Props

Marketing Mavericks
Episode #29: Trey Ratcliff October 30th, 2014

HDR Photography, blogging and creative commons pays off

Tech News Today
Episode #1125: Cook Out October 30th, 2014

Samsung reports miserable quarter, Microsoft announces fitness band, Tim Cook comes out, and more.

Ham Nation

Bob Heil shows how to DX on a vintage station.

This Week in Google

Larry Page hands leadership of many Google products to Sundar Pichai.

Tech News 2Night

Moblie Payment Terminal Wars

iFive for the iPhone

Siri location tip, landscape keyboard.

Windows Weekly
Episode #386: Pom Pom Paul October 29th, 2014

MS Office 15 in 2015 and a $50 Xbox One Holiday price cut.

FLOSS Weekly
Episode #314: CoreOS October 29th, 2014

Linux for Massive Server Deployments.

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.