Page 3 of 13

1. Introduction
2. Object Orientated Programming
3. Namespaces
4. A Class in Objects
5. A House Building Class
6. Let's Up The Variables' Property Value A Bit
7. Quick Structs
8. Inheritance
9. Lest we become Abstracted
10. Parameters & Overloading
11. Interfaces
12. Finally Polymorphism
13. Conclusion

Comments

1. Yoenuts
   25 Jul 2006 at 13:14

   hello,
   
   
   I am very impressed by your tutorial as it finally allowed me to grasp the syntax behind OOP programming with .net.
   Only what I did not understand is how and where do I complile the .cs to a dll? I cannot do it on the server. Do I do it on my local computer and then upload?
   
   
   http://www.developerfusion.co.uk/show/4341/5/

2. Gabor Gorcsos
   22 Jun 2006 at 06:29

   Honestly I believe that the basic idea of the OOP was really great, but to be able to use it one really has to have the head as a water melon. There is too much theory, too many therms and the class theory really feels like puting each part of the program into a separate box and then figuring out how to drill a way between them. I started to learn C++ OOP at least 20 time and after a couple of weeks I did not even had an idea what it is about (note: I am not a proffesional programmer)...

   I believe that: "The use of a programming language should be as simple as a pie and the algorithm should be the part where people spend the most of their time..."

   When I do C# programming I do all public and it works great for me. Simply keep it simple!!!

   Is there any web page or book where I could find how to do Non-OOP C# programming?

   Sincerely,

   Gabor Gorcsos

    

    

    

3. James Crowley
   20 May 2005 at 23:21

   Though from personal experience I'd say 99.99% of the time, you'd want private member variables and public properties...

4. Dimitrios Markatos
   22 Apr 2005 at 18:00

   Hi Ehx,
   

   
   That's true, and it's funny that in all my other articles I always write all private variables with public properties. i.e. - Building a Full-Featured Custom DataGrid Control. It's just one of those overlooked things. Oh well.
   

5. aalhussein
   22 Apr 2005 at 17:26

   After reading your article, http://www.developerfusion.com/show/4341/6/
   I got realy confused!!
   

   
   from what I know from the book below, I declare private property, then declare public (get , set )
   What you presented in your article is you declared public property,then  made the (get,set) private)
   

   
   I have put this simple comparison code , so please advice your point, What is the logic behind reversing the modifier(public to private and vis versa).
   thanks
   Ehx
    
       // what is in the book (Begining Asp.Net Database using C# p 321)
          private string Country;
          public string Country
          {
              get{return _Country;}
              set{Country= value;}
          }
   

   
                 // what is in web article ( in your article)
          public string Name;
          private string _Name
          {
              get{return Name;}
              set{Name= value;}
          }

6. Developer Fusion Bot
   01 Jan 1999 at 00:00

   This thread is for discussions of The Quick & Dirty .NET Guide to C#/VB OOP.

Dimitrios, or Jimmy as his friends call him, is a .NET developer/architect who specializes in Microsoft Technologies for creating high-performance and scalable data-driven enterprise Web and deskto...