| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Inheritance from a Base Class in Microsoft .NET | |
|
||
| Time: 15:10 EST/20:10 GMT | News Source: Microsoft | Posted By: Robert Stein | ||
|
"One of the key features of Object Oriented Programming (OOP) languages is inheritance. Inheritance is the ability to use all of the functionality of an existing class, and extend those capabilities without re-writing the original class. Prior to the availability of Microsoft® Visual Basic® .NET, Visual Basic programmers did not have this capability. In Visual Basic .NET, you are able to inherit from classes that ship in the Microsoft .NET Framework, as well as from classes that you create. In this document, you will learn how to use inheritance, and see how it can significantly cut down your programming time." | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 311 Last | Next |
The time now is
10:04:21 AM
ET.
Any comment problems? E-mail us |
| #1 By 135 (209.180.28.6) at 12/27/2001 4:59:55 PM |
|
Oh great, the ignorant are back to bash VB again...
|
| #2 By 1845 (12.254.240.94) at 12/27/2001 11:18:54 PM |
|
That is a very interesting analysis #13. I agree with you on most points. I happen to be a web developer most of the time though, so I must defend those of us that know how to code and get stuck with VB/VBScript. As soon as the .NET framework was released last August (the version that shipped at PDC 2000) I downloaded it and started playing wtih ASP+ (as it was then called) in C#. Coding just gets better and better.
For the most part, though, the projects I get to maintain written by other web "developers", are more spagetti than code. The first ASP project I worked on I eliminated about a quarter of the previous developer's "code" on the first few weeks. He was an IS guy that said, hey, scripting is easy, why don't I learn it as I go. The best analogy I have for a developer coding in VB is this - it's like the CEO of a Fortune 100 company signing a check with a crayon. Yes, it does the job, but... it just isn't a very elegant solution. |
| #3 By 1845 (12.254.240.94) at 12/28/2001 12:30:46 AM |
|
Programming for money is about making money. There is a quite a bit of code written these days for altruistic reasons. Aside from that, I agree with you to a point, but...
Writing version 1 of a product in VB that can't easily be extended to produce a version 2,3,4, etc. is not always considered in the business world. One reason managers (who aren't developers) may not give respect to programmers is because they don't understand good coding practices. For instance, every book or article on object oriented design will say that you should design with inheritance in mind. You do this for code reuse, simplified debugging, etc. In short you do this to benefit the current project. Many managers don't see past this point. A good developer will design his code to benefit future projects. Others won't have to reinvent the wheel if his object model is extensible enough. Also, though, he has to take extra precautions because others who don't know his code, may be those who extend it. A good developer will design the project for the next versions as well. He will write his components, in terms of how he will use them, and how others will use them too. It is not wise to say, let's get this problem solved as quickly as possible and think no further. You must also think, how can I design this so that others can reuse this code too. Designing code in this fashion is elegant. In the long run, the more elegant solution is usually the most cost effective. I wish more managers had a computer science background, so that they could understand this. |
| #4 By 1845 (12.254.240.94) at 12/28/2001 12:31:00 AM |
|
dp This post was edited by BobSmith on Friday, December 28, 2001 at 00:31. |
| #5 By 1845 (12.254.240.94) at 12/28/2001 12:34:14 AM |
| #16 That's just what I was trying to say. :-) |
| #6 By 135 (208.50.201.48) at 12/28/2001 1:22:18 AM |
|
#13 - A qualified developer should be able to write solid code in any language put before them.
I've been programming off and on since long before there was a C++. We used Pascal in school, and our OOP training was done in Smalltalk and CLU(I had professor from MIT). Most of my professional development experience was in C on Unix systems. I don't particularly like C++ because I find the grammar to be an absolute horrid nightmare. It has nothing to do with being lazy or untrained, I simply do not like it. This is exactly why Java became popular, because it has a much better grammar and will accomplish 95% of what most people need to do. The same is true of C#. Now I attended a lecture by a local author Rocky Lohtka regarding VB.Net. What I came away with was just how impressive the new version of VB is. Why? Because they cleaned up a lot of the crap that was in VB6 which broke rules of orthogonality, symmetry and so forth. It's just as elegant a language as is C#. As #10 said, they are really the same language in many ways. The only difference is the syntax and grammar. Whatever, I'd like to see your "training" credentials. I suspect I'm not the untrained one here. |
| #7 By 135 (208.50.201.48) at 12/28/2001 1:33:06 AM |
|
More comments.
#16 - Having requirements, specification and design has nothing to do with C++ versus VB. It still has to be done. In the end though, depending on the app purpose, it is still frequently easier to build and deploy the app in VB than C++ most oftentimes by at least a factor of 2. #17 - BobSmith, again this has nothing to do with VB versus C++. The same principles of design hold true for any language. #20 - is absolutely correct. #22 - is absolutely correct. ASP is the glue to time COM components together. Spaghetti code written in ASP is a sign of someone with lack of experience, nothing more. It's interesting but we still have not gotten to the bottom of why people hate VB. Thus far there has been no discussion of the language itself, but rather of a select few people who call themselves developers who have tried to use it. Again, the same is true of any language. I also don't particularly like the attitude of "We must make it difficult, for then only the strong shall survive" inherent in C++. It reminds me of the arrogant attitude of Linux developers towards endusers, calling them lusers, etc. In my world, if something is difficult the goal should be to make it easy. If something provides too much rope to hang yourself, then the goal should be to fix the rope. Computers should not be hard to use, they should just work. It's my ultimate goal to put myself out of a job. That should be the job of any person building automated computing systems. |
| #8 By 2332 (165.247.1.179) at 12/28/2001 5:52:48 PM |
|
Guys... any opinions of Visual Basic based off VB6 (or earlier) are simply irrelevant in the world of .NET. Period.
Personally, I'm using C# because it's less verbose in its syntax - but that's a matter of preference and has little impact on code quality or application quality thanks to things like intellisense. As far as the many opinions about VB6, you're all entitled to them - but I disagree. Visual Basic 6 is a great langauge to quick solve problems with. It's perfect for the IT Professional who wants a tool that gives them access to nearly all of the programming universe, but with little or none of the headaches. |
| #9 By 135 (208.50.201.48) at 12/28/2001 11:14:12 PM |
|
#33 - Your comment has nothing to do with VB.
|
| #10 By 2332 (165.247.10.124) at 12/29/2001 12:52:22 AM |
|
#33 - Ah, ok... so the technology can't be too easy, or too hard... either way is bad for "real" programmers? Wow.
I'm an IT professional, but I'm also a programmer. See, I wanna make sure I can cut people like you out of the loop. :-p |
| #11 By 1845 (12.254.240.94) at 12/29/2001 4:28:45 AM |
| It makes sense to me #36, but I somehow don't think the others hear what you are saying. |
|
Write Comment
Return to News |
Displaying 1 through 25 of 311 Last | Next |
The time now is
10:04:21 AM
ET.
Any comment problems? E-mail us |
