Upgrading VB5 application to VB.Net or C#
-
Hi, I have a large VB5 application that needs to be moved to .Net. I am considering 3 options to upgrade the application. 1) Upgrading to VB6 first and then using the wizard to upgrade to VB.Net 2) Rewrite the application in VB.Net 3) Rewrite the application in C# Does anyone have any advice for taking this application to .Net or have any experience taking a VB5 application to .Net. Thanks
-
Hi, I have a large VB5 application that needs to be moved to .Net. I am considering 3 options to upgrade the application. 1) Upgrading to VB6 first and then using the wizard to upgrade to VB.Net 2) Rewrite the application in VB.Net 3) Rewrite the application in C# Does anyone have any advice for taking this application to .Net or have any experience taking a VB5 application to .Net. Thanks
Take option 2 or 3. VB6 is a very different language, the upgrade tool plain does not work, nor can it.
Christian Graus - Microsoft MVP - C++ "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
Hi, I have a large VB5 application that needs to be moved to .Net. I am considering 3 options to upgrade the application. 1) Upgrading to VB6 first and then using the wizard to upgrade to VB.Net 2) Rewrite the application in VB.Net 3) Rewrite the application in C# Does anyone have any advice for taking this application to .Net or have any experience taking a VB5 application to .Net. Thanks
The elegant approach: 1) Pick up the logic from the specs of the application or a bit of reverse engineering/study of the application. 2) Plan out the implementation in (3). :) I don't subscribe to implementing in (2). It sucks. :mad:
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
Hi, I have a large VB5 application that needs to be moved to .Net. I am considering 3 options to upgrade the application. 1) Upgrading to VB6 first and then using the wizard to upgrade to VB.Net 2) Rewrite the application in VB.Net 3) Rewrite the application in C# Does anyone have any advice for taking this application to .Net or have any experience taking a VB5 application to .Net. Thanks
Have a look here: VB Fusion - Extend Your Visual Basic 6.0 Applications[^] The video: "When to use Visual Basic Fusion" discusses what path to take depending on your scenario.
Kevin
-
Hi, I have a large VB5 application that needs to be moved to .Net. I am considering 3 options to upgrade the application. 1) Upgrading to VB6 first and then using the wizard to upgrade to VB.Net 2) Rewrite the application in VB.Net 3) Rewrite the application in C# Does anyone have any advice for taking this application to .Net or have any experience taking a VB5 application to .Net. Thanks
Having worked with all I would go with option 3. Rewriting and then converting is going to give you a ton of errors that you may as well start from scratch. This will also give you the ability to look at .NET features to see what you can rewrite to make the program more robust and faster.
_____________________________________________ Flea Market! It's just like...it's just like...A MINI-MALL!
-
Hi, I have a large VB5 application that needs to be moved to .Net. I am considering 3 options to upgrade the application. 1) Upgrading to VB6 first and then using the wizard to upgrade to VB.Net 2) Rewrite the application in VB.Net 3) Rewrite the application in C# Does anyone have any advice for taking this application to .Net or have any experience taking a VB5 application to .Net. Thanks
Depending on what kind of app you are wanting to make, I'd go with options 2 or 3. I usually use VB.NET because it is easy, intuitive, and quick to write. If you are going to make a robust, thorough, or big app, then go with C#. It is MUCH faster, especially with dealing with many numbers. In summary, I personally would choose VB.NET, simply because I don't know how much better C# is. If you're a beginning or advanced programmer looking to build a medium sized or large app, use C#. If it's just a simple app, use VB.NET. It's easy and fast. Besides, usually you don't need the speed.
-
Depending on what kind of app you are wanting to make, I'd go with options 2 or 3. I usually use VB.NET because it is easy, intuitive, and quick to write. If you are going to make a robust, thorough, or big app, then go with C#. It is MUCH faster, especially with dealing with many numbers. In summary, I personally would choose VB.NET, simply because I don't know how much better C# is. If you're a beginning or advanced programmer looking to build a medium sized or large app, use C#. If it's just a simple app, use VB.NET. It's easy and fast. Besides, usually you don't need the speed.
`Drew wrote:
It is MUCH faster, especially with dealing with many numbers.
Since both C# and VB.NET compile to the same MSIL, there really isn't any difference. Care to back that statement up with a benchmark?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
`Drew wrote:
It is MUCH faster, especially with dealing with many numbers.
Since both C# and VB.NET compile to the same MSIL, there really isn't any difference. Care to back that statement up with a benchmark?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Well, it's not really a benchmark, but it may serve the perposes of making a point. I have a project purchases program. Each time it loads, it goes off and gets > 45,000 records, sorts them, and conveniently displays them in a hierarchy. With C#, it doesn't matter whether you load the tables or not because each takes roughly the same time. With VB.NET, it'll take a few seconds to load the same database. Please note I coded nothing in either as Visual Studio does it all.
-
Well, it's not really a benchmark, but it may serve the perposes of making a point. I have a project purchases program. Each time it loads, it goes off and gets > 45,000 records, sorts them, and conveniently displays them in a hierarchy. With C#, it doesn't matter whether you load the tables or not because each takes roughly the same time. With VB.NET, it'll take a few seconds to load the same database. Please note I coded nothing in either as Visual Studio does it all.
Designer generated code isn't necessarily the same. The only "proof" that would demonstrate this with any accuracy is if the database code was written by hand.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Designer generated code isn't necessarily the same. The only "proof" that would demonstrate this with any accuracy is if the database code was written by hand.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Dave Kreskowiak wrote:
Designer generated code isn't necessarily the same.
Considering my part of the program is < 50 lines long (C#)(about 10 in VB.NET), it shouldn't matter, should it?
Dave Kreskowiak wrote:
The only "proof" that would demonstrate this with any accuracy is if the database code was written by hand.
Of course it is. Is there any other way to do it?
-
Dave Kreskowiak wrote:
Designer generated code isn't necessarily the same.
Considering my part of the program is < 50 lines long (C#)(about 10 in VB.NET), it shouldn't matter, should it?
Dave Kreskowiak wrote:
The only "proof" that would demonstrate this with any accuracy is if the database code was written by hand.
Of course it is. Is there any other way to do it?
There is no significant performance difference between VB.NET and C#. If you wrote two versions of the same app and one performs better than the other, then the most likely explanation is that you wrote the code differently. I remember an example from way back when from Borland who claimed that Delphi was faster than VB and provided a benchmark that 'proved' it. But when you actually look at the code, they were comparing integer operations with floating point operations. Of course, integer operations are faster than floating point operations. Whether knowingly or unknowingly, their benchmark test was invalid. Post your code here and I'll tell you what you're doing differently.