.comment-link {margin-left:.6em;}

Pranav Wagh's Blog

Tuesday, December 20, 2005

What's in Visual Basic 2005 for the Visual Basic 6.0 Developer

I admit that when I tried to create my first VB.NET application I wasn’t that comfortable, and when I tried to convert my VB 6.0 application in VB.NET, the upgrade wizard failed for even the simplest things, I always missed old VB, but now it seems that the world is changing with VB .NET 2005 read on in the words of Scott Swigart  the complete stuff is on http://msdn.microsoft.com/vbasic/default.aspx?pull=/library/en-us/dnvs05/html/VB05forVB6.asp

 

I Haven't Needed .NET for Anything so Far...

The Microsoft Hype Machine has already started turning up the volume on Visual Studio 2005. The question is, if you work primarily in Visual Basic 6, you're happy with Visual Basic 6, and you've looked at .NET and not found anything you really need, should you even care about this new release of Visual Studio 2005? Considering that MSDN has been nice enough to host this article, you can probably guess the conclusion that I've reached. But bear with me, there are some great things coming for the Visual Basic 6 developer.

First of all, let's just admit that for many of us, Visual Basic .NET left something to be desired. If you think back to when Microsoft unleashed .NET on the world, the megaphone was blaring only two things: Web Service and C#. Well, many of us Visual Basic 6 developers, didn't need (or even want) Web Services. And, we weren't really interested in learning this new C# language when we already had a good language. After Web Services and C#, the other thing that Microsoft was blaring was ASP.NET. While many of us do some Web development, lots of Visual Basic 6 developers are primarily interested in desktop applications, so if .NET was all about Web Services, C#, and ASP.NET, then Microsoft should understand if many of us did not find anything in .NET that we couldn't live without.

Finally, let's just say that Visual Basic .NET wasn't 100 percent compatible with Visual Basic 6. This made it non-trivial to move a Visual Basic 6 application to .NET, assuming that I wanted to.

 

”   

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home