Paul Vick - Why would a VB 6.0'er consider VB.NET?
- Posted: Oct 12, 2004 at 6:57 PM
- 40,406 Views
- 4 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
If you're a Visual Basic 6.0 programmer, why would you consider moving to VB.NET? Paul Vick, technical lead (translation: smart dev) on the Visual Basic team talks to us about the trials and tribulations of learning VB.NET from the VB6'er point of view.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
--
wjs mvp
Like a tree-hugging hippie liberal, I refused to learn pointers becuase they were ugly. I could have went for the money and forced myself to learn C++ but I knew the language was not designed from the ground up for my first love OOP. C++ brings you closer to the patchy Windows OS---too close for me.
Before the wonderful arrival of C#, I was a VBA/VB6/tSQL guy---but I also was a JavaScript guy and loved to build relatively complex JavaScript/HTML apps (thanks to the sage teachings of Danny Goodman). It was this JavaScript syntax that prepared me for the angle-bracket "strangeness" of C#.
I can tell by the way RegisterClientScriptBlock is implemented in ASP.NET that most programmers of the Visual Studio world don't have a deep understanding of JavaScript (JScript)---and VB.NET guys, I assume, really don't care about JScript. And in here lies my accusation of the VB.NET design team and their use of the keyword My:
VB.NET developers are not required to be concerned about the theory behind what they are doing. They can just write and write and edit and continue and the development environment will try its level best to guess what the theory is behind what they are doing and help them out as best as it can. For most VB programmers I am convinced this works out just fine---and, in VB.NET, they are not prevented from being more serious and more formal once they decide to get whiteboard theoretical.
Ditto.
Remove this comment
Remove this thread
close