@stevewp8dev: Hmm... yeah, if you don't have any colloquialisms that differ by region regardless of language, I guess you can just click them all.
|Site Feedback||Thanks for the Absolute Beginner Series!||37||Aug 10, 2013 at 8:49 AM|
|Coffeehouse||Visual Basic Express Edition Fundamentals||5||May 21, 2012 at 11:26 AM|
@nsnavare: I think the point I am laboring to make is this ... VB gets compiled down to the same IL as C# and other managed languages. In that regard, it is no different from C#. However, there's a different culture around C# than VB. This speaks to the quality of reference materials available. For example, look on the http://www.asp.net website ... there are no VB examples. On Microsoft Virtual Academy -- most topics are only covered in C#. At TechEd or Build conferences, I can't remember seeing a speaker use VB to demo a given feature. Most books only have source code examples for C# for a given topic. Most StackExchange answers are provided in C#. So, again, I'm not disparaging the language. It is sufficient to handle virtually any task that C# can handle because they use the same tools. The true difference is in the experience as a result of the Microsoft development community at large. Hope that makes sense.
Just to be clear, VB *is* different from C++ because you can create either managed or unmanaged C++ applications.
Sep 25, 2014 at 2:01 PM
@Juan Jose: Could you post your code AND let me know which line / part you saw the red squigglies under? Thank you.
@stahtufiang: Thank you for the good thought. Let me explain my rationale. (1) Keep in mind, this series is for absolute beginners with no programming experience at all. In less than eight hours we go from 0 to LINQ ... that's a huge leap. The fact that generics is something you want to know makes me guess this isn't your first rodeo, so to speak. You have programming experience already, correct? (2) Microsoft has a budget on what they're willing to spend, so somethings can stay and some things have to go. (3) IMHO, generics is not a beginner level topic. In fact, IMHO generics goes to the bottom of the list behind more OOP topics like interfaces and dependency injection. I mean, you definitely need to know what to stick between the angle brackets (that's why I say "you make a generic specific by giving it a data type"), but beyond that I think you're ok with just understanding it at a surface level.
There are many series on Channel9 and MVA that can take you from here to that next level. Actually, my personal regret:I should have added something about async because you can't use WinRT or many of the new .NET API's without it.
Thank you again for your comment. If we ever do this series again, I'll be sure to give that some serious thought.
@Tony: I would say that you should not be discouraged when it comes to classes. Just accept the fact that they're used and how to create new instances of classes as created by Microsoft in the .NET Framework class library. Frankly, it took years before it really clicked for me (I'm slow). So, again, don't get discouraged. Just plug away a little every day and keep trying to consume explanations from different authors. Good luck!
Sep 08, 2014 at 1:36 PM
@Shawn: I've been compared to many people but never Quintin Tarintino. :) But, thanks?
C# Fundamentals for Absolute Beginners: (17) Working with Classes and Inheritances in the .NET Framework Class LibraryAug 21, 2014 at 7:32 PM
@Chowdary486: Your code DOES WORK! You added a second Console.ReadLine() therefore you MUST HIT THE ENTER KEY A SECOND TIME to see the Mytruck print out. :)
You do have one error in your code ... BMW doesn't make a C class. :P
@NETdeveloper: Hi, please double check ... go to Help menu, choose About at the bottom ... the About dialog pops open.
Make sure that it says EXACTLY this in the top left side of the dialog:
Microsoft Visual Studio Express 2013 for Windows Desktop
If not, type in EXACTLY what you see in your About window.
C# Fundamentals for Absolute Beginners: (17) Working with Classes and Inheritances in the .NET Framework Class LibraryAug 12, 2014 at 1:48 PM
@arifuddin: I've not read that book, so I can't comment. The focus of this lesson is to explain how Microsoft uses classes ... how one class inherits from another class. They build a class that has basic functionality, then create other classes with more specialized / advanced functionality based on the original. If you can understand that basic idea, you've gotten enough out of this lesson. Don't worry about creating inheritance hierarchies in your applications ... that would require a bit more time and explanation as to why and how you do that.