Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
One of the hottest questions that you get about .NET is exactly how and when and why should we upgrade? And Microsoft is just now really started to offer some more useful information on this, but of course that's just kind of coming with time as people deal with that. There are obviously advantages to upgrading to VB .NET, number one scalability, especially on the ADO side where you're connecting to databases. The new constructs out there like data sets and data adapters and so forth. We have disconnected data from our databases, and it's just a lot more scalable for your applications, especially the web based ones. Performance obviously is better in .NET and then the deployment is greatly simplified in .NET. And depending on the conditions, it could be as simple as just x copy, and just copying files to hard disk. Now the ease of the upgrade: nobody really said that this is going to be easy. .NET as you've already seen in the course is just such a drastic difference from Visual Basic as we knew it. About the best thing that helps you is the modularity of your code in VB6. If you stuck as hard as you could to object oriented principles in VB6 it makes it easier. Because it's easier to get chunks of the code working. The different project types that you have also create issues. Some of the old project types simply don't map to anything in VB .NET, for example activex controls, activex documents and so forth simply do not have a counterpart in VB .NET. All that functionality is rolled into the Framework itself, and you build most of that stuff in web forms now. The best thing to do in upgrading to VB .NET is a complete rewrite. Now that sounds expensive, but what most people seem to be opting on with .NET is to leave their VB6 apps where they are in place. And then as they begin to phase these out, or come up with projects, they move to VB .NET and totally begin from square one, writing these things in VB .NET. Now I've heard of a few companies who are now scheduling rewrites on current applications. Now I guess the second choice, the better one is a complete upgrade, and this is where you completely upgrade all aspects of the program. Now upgrades can be time consuming. and I also have to talk about why in the next video, but you are going to get a list, probably a long list of things that have to be corrected, and somebody has to correct those and then test them. And then the good solution is a partial upgrade, now a partial upgrade unfortunately is usually where you end up if you don't do a complete rewrite. Because on a partial upgrade, that simply means we tried to upgrade it but parts of it just wouldn't go. And so parts of it are in VB .NET and other parts are still out in VB6. So that's just going to be a something you'll have to deal with. Upgrading is a tough issue; again I have to be honest with you, I think probably the easiest issue is just to let the old one ride and rewrite it, using VB .NET. Now of course there are a lot of people who would disagree with that for various reasons. Keep in mind Microsoft seems to be indicating in their printed material, rewrite is the best way to go. They do have an upgrade wizard, we are going to talk about that in the next video and it does help. And probably in time we'll start to see third party apps and even maybe something from the Microsoft's resource kits or something to really help with this upgrade area. So that's a quick overview of upgrading. In the next video we are going to talk about the upgrade wizard and some specialties about that.
| Course: | Microsoft Visual Basic .NET |
| Author: | Mark Long |
| SKU: | 33433 |
| ISBN: | 1932072349 |
| Release Date: | 2003-05-27 |
| Duration: | 6 hrs / 87 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |