A group blog from members of the VB team
This webcast series is devoted to those who want to learn to really use Visual Basic and what it can do! Learn from Ron Cundiff, Developer Evangelist and featured Microsoft speaker.
This is a 20+ part series that's underway. Check out the on demand recordings and sign up for the live webcasts here.
-Beth Massi, Program Manager VS Core Community
I signed up for the on demand webcasts online but do not see a link to download them for later viewing. Are these available for download or only streaming in Live Meeting?
Yes you can download the webcasts by clicking on the "Click to download Live Meeting Replay for offline viewing." link and select "Save As" when the browser prompts you. That will download the WMV file for you.
"who want to learn to really use Visual Basic and what it can do! "
The very first programing lanauge that i learned during College was Visual Basic 5 but today's VB(VB.net) is vastly different from the VB that i used to know.
when i in VB.net, it make me feel like i'm programing in C#! Why do MS even prompting VB.net to VB developers? Can't MS just tell the truth?
Dear Developers, we have turn VB into C/C++/C# like lanauge and it will be better off for you to learn C# instead of VB.
I don't even understand why MS is keeping VB alive.
I think the webcasts series could help you learn VB and .NET so you should try it out. Ron starts out the series with a basic introduction of the different types of applications you can write, including web applications, and does it all from notepad (http://msevents.microsoft.com/cui/eventdetail.aspx?eventID=1032326143&Culture=en-US).
The second webcast walks through the features of the free Visual Basic Express IDE (http://msevents.microsoft.com/cui/eventdetail.aspx?eventID=1032326167&Culture=en-US) which should help get you started.
Then you can learn about language and OOP fundamentals, controls, application structure, and take off from there (http://www.microsoft.com/events/series/msdnvb2005.mspx) . You can also check out the virtual labs that let you work with the products and play with them yourself which also may help you learn.(http://msdn.microsoft.com/virtuallabs/vbasic/default.aspx)
you missed my point. when i code in VB.net it feel like i'm coding in C#. both lanauges are very similar and VB.net is vastly different from old VB.
what is MS doing with VB.net that is different from C#? NOTHING! MS take away all the things that old timers like me love about VB and turn it into C++/Java/C# like lanauges.
Why is MS still promoting VB? Why not just killed it? There are NOTHING in VB.net that make me want to use it. VB.net lost all its orginial flavors. It yet another dead lanauge support by MS to write .Net code.
I rather code in C# than VB.net because there is no different between the two. Can you give me some good reasons why i should code in VB.net and not C#? What does VB.net have to offer that i can't do in C#? the My class in VB.net is ok but that's not enought to make me switch back.
What is your team doing with VB that is different from C#? Why should i go back to VB again?
Huh? I hope you don't mean that OOP is a C++/Java thing that they own. VB isn't like C#, VB and C# are like .NET languages. They are like CIL and do (with many exceptions) what the underlying platform does.
For the record VB has about 5-10x as many specific language features that C# doesn't have. The value of those features in many situations is debatable but I definately wouldn't want to code for Office in C#.
The point remains, I like VB.NET - a lot - so if there are people who use it and like it, why should they take away my favorite toy for you? Why is your disapproval more important than my approval?
This is my point of view and I might be wrong, both VB.NET and C# are .NET language. For VB developers to shift into .NET language VB.NET is the route. For Non-MS developers who wishes to shift into .NET language C# is the route.
Some VB developers are comfortable and happy shifting from VB to VB.NET, its a developer choice whether he/SHE goes to C# or VB.NET. Just like you, you prefer to use C# rather than VB.NET.
Does this answer your question?