Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What version do I need to upgrade a vb6?

Status
Not open for further replies.

lordhawkins

Programmer
Sep 25, 2003
64
SV
Ive installed VB.Net Standard (2002). When I try to open a project made with VB6, it says that "this version can convert from Visual Basic 6".
Do I need to spend on another version?
Exists out there a solution on the form of a patch service pack or other stuff?
 
I would guess you need Professional, but I'm not sure. All in all though I would recommend NOT converting your VB6 code. VB.Net is a completly different programming language. Yes it shares a lot of syntax with VB6. But .Net is fully Object Oriented, and as such the logic behind design decisions is vastly different. Running the converter from VB6 to VB.Net will make the updates to the syntax, but the design will still be the old VB6 design and will not function correctly (in the vast majority of situations). I would recommend instead, start from scratch. Use the old application and user feedback to re-establish goals and requirements. Come up with a complete object orriented design. and build the app in VB.Net

-Rick

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
[monkey]I believe in killer coding ninja monkeys.[monkey]
 
The problem is that the company got a big & expensive (and turtle slow) system created with VB6. My idea is use VB.Net to improve the performance and the developing environment. Creation of the original app has taken 3 years, to another programmers's team.

Really do I need to recreate everything?
Could I include the project as a subproject in the solution?
 
Using a converter tool to move the project to VB.NET isn't going to have any kind of performance boost on the system. Re-evaluating the requirements and goals of the system and then designing the system from there is the only real way of getting the benefits from VB.NET.

If you don't have the option of re-creating the project from scratch I wouldn't bother even converting it - it may as well still be a VB6 application.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 
There may be a middle path. Does the VB6 code expose any COM objects or interfaces? You may be able to keep the existing code there, and wrap it in a VB.NET layer to get some object-oriented goodness out of it.

Chip H.


____________________________________________________________________
Donate to Katrina relief:
If you want to get the best response to a question, please read FAQ222-2244 first
 
But that won't make it much faster.

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]
 
Well... tnx to all for answering. Resuming your posts, everybody recomends against an "upgrade" because the code won't lends itself to it.

There are no COM objects inside it, from my knowledge, then no code to salvage.

Remember that the app was made by other team. I knew the guys, but contact may prove hard. Sigh...

Well I'm back to square one, and have to read all the app.

But...
Could I try just to convert the code with VB.Net Standard? Or do i need another product (VB.NET Pro)?

those guys never tire? [wiggle][wiggle][wiggle]
 
Hawkings, have you ever used Altavista's Babble Fish? Or Google's page translator? The do a great job a replacing common words from one language to another. But if you take a phrase like

"The fat and lazy dog munched merrily on a grass hopper" and run it through the translator to a language and back to english, you get something like "The sluggish fat as the dog chewed cheers on a grass distributor"

This is kinda what the VB6 -> VB.Net translator does. It replaces the words, but the meaning is often lost. The translator can work perfectly, if the VB6 app was designed perfectly in an OO patern. The likelihood of that is virtually nil, because VB6 was not a full OO language and so the best and most common practices where not OO designs.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
[monkey]I believe in killer coding ninja monkeys.[monkey]
 
I wouldn't upgrade it unless they wanted it re-written from the ground up anyways. Then I would rewrite it in VB.Net. I would stick to creating new applications in VB.Net for now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top