🔒 Locked

Visual Basic .NET questions

Started by Ilici May 11, 2004 at 3:28 AM 1 reply 400+ views

Original Post

205

May 11, 2004 at 3:28 AM

Hello I''ve been working with Visual Basic 6 for some time and I''m now interested in the .NET version. However i''m not sure about the way i can convert my work from ver 6 to .NET, as this would influence my decision to buy this software. So, can I import VB 6 projects into VB.NET? I''ve read some information about an Upgrade project feature that VB.NET has. Is this feature fail-safe - it will convert a working VB6 source into a fully working .NET source?

Manip

May 11, 2004 at 3:51 AM

Go google for ''Microsoft Code Anviser'' (VB6 app)

http://www.microsoft.com/downloads/details.aspx?FamilyId=A656371A-B5C0-4D40-B015-0CAA02634FAE&displaylang=en

daveangel

May 11, 2004 at 5:15 AM

yeah use the vb6 plugin manip said it works pretty good and will tell you which parts of your code you need to fix for it to compile under .net vb.
But suffice it to say this can be get pretty hairy so microsoft even has a book called "upgrading vb6 to .net vb" that covers most of what can go wrong.
Well here is part of what it says:
The Upgrade Wizard will either not upgrade or provide only partial support for the following items:

ActiveX EXE projects

Designers such as Add-In Designer, DHTML Page Designer, DataReport, and DataEnvironment

Certain ActiveX controls: SSTab and UpDown

ActiveX document–based applications

Extensibility model–based applications

OLE container control

Drag and drop

Graphics statements and graphical controls

Dynamic Data Exchange

In terms of upgrade potential, is your application in or out? As discussed in this chapter, the situation really depends on the type of Visual Basic application you’ve written. If your application drives the Visual Basic 6 extensibility model, uses an ActiveX designer such as the DHTML page designer, or relies on Dynamic Data Exchange (DDE), it’s in the out category. You’ll need to do a significant amount of rewriting to make your application work in the .NET environment. In some cases, it might make more sense to leave your application running in Visual Basic 6 and interoperate with it from Visual Basic .NET.

If, on the other hand, your application is a more typical three-tier application with a presentation layer that communicates with a server component, it’s most definitely in the in category. You’ll find that the Upgrade Wizard does a good job of upgrading applications that fall into this category. The Upgrade Wizard will strive to upgrade your application in the least intrusive way possible that will allow you to get it up and running quickly. Using the Upgrade Wizard, you will be able to get your Visual Basic 6 application up and running in Visual Basic .NET more quickly than by porting your Visual Basic 6 application by hand.

If God played dice, He''d win.
—Ian Stewart, Does God Play Dice? The Mathematics of Chaos

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.