Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

I understand that VB.Net comes with a utility to convert VB6 code into VB.Net code. I was wondering if anyone had had any experience of using this, and, if so, how effective it is.

 

I also understand that the utility doesn't do everything that is needed. If you have quite a large and complicated program (say around 30,000 lines with half a dozen dlls), can you give an estimate of how much time it would take a developer to finalise the conversion?

  • *Experts*
Posted
The converter produces a non standard code, like default instances and things like that from VB6 that shouldnt be used in .NET. Most people here will not suggest using it. If your program is very big and works then you shouldnt have to convert it. If its small and could use some of the new functionality then you could rewrite it yourself.
Posted

I have used the conversion util on quite a large application. I knew I was going to have to port it across, so followed M$ ideas on how to keep to at a standard that would allow an easier conversion. My app was about the same size as you have mentioned, and took probly bout a week to move across to a basic version.

 

The app was mostly code based (server engine) so not many dependencies on forms (which you have to basically rewrite from scratch). You may also find that some of your code needs re-writing just to use the new methods (like inheritance was a biggie for me).

 

You gain new issues like 3rd party controls, that have to be either in .net or prey they work well with an Interop version. Dlls are loaded differently, and give you a few hassles, but its a one of thing to fix. .Net uses multithreading as a standard, so watch out for timers and events happening at the same time, especially if you use 3rd party controls created in .net.

Posted

If you're upgrading programs from Visual Basic 6 you can use this:

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

 

It's a Code Advisor Toolbar for Visual Basic 6, it can run through you're project and tag parts that won't upgrade correctly or shouldn't be used so you can fix it or know where to expect problems.

.Net allows software to be written for any version of Windows and not break like Unmanaged applications unless using Unmanaged procedures like APIs. If your program uses large amounts of memory but releases it when something else needs it, then what's the problem?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...