CHOTD [modified]

leppie

I have been given a VB6 project to upgrade to C# :(( :sigh: :( [update] VB6 to VB.NET conversion ======================== - 400 Upgrade warnings - 100 Compiler errors - 2 Missing dll references... [update] [update2] VB.NET to C# conversion ======================= - 2064 errors [update2] -- modified at 6:29 Monday 22nd October, 2007 -- modified at 11:20 Monday 22nd October, 2007

xacc.ide
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."

DavidNohejl

leppie wrote:

I have been given a VB6 project to upgrade to C#

Bah, that's nothing. Or null. Or empty. ;P

[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe

originSH

Surely this is better than being given a C# app to downgrade to VB6? And better than being given a VB 6 to maintain.

J4amieC

Better that than the other way round

--- How to get answers to your questions[^]

Tristan Rhodes

That's was a pretty big typo there ^^ Nice Rule btw

------------------------------- Carrier Bags - 21st Century Tumbleweed.

Vasudevan Deepak Kumar

leppie wrote:

- 400 Upgrade warnings - 100 Compiler errors - 2 Missing dll references...

Wouldn't such a mammoth statistics suggest going for a fresh VB.NET development rather?

Vasudevan Deepak Kumar Personal Homepage Tech Gossips

leppie

I think the application has less lines of code than errors, so yes I am pushing for a fresh C# app :)

xacc.ide
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."

Xiangyang Liu

leppie wrote:

- 400 Upgrade warnings - 100 Compiler errors - 2 Missing dll references...

I don't understand how this can be classified as a "coding horror". If you copy VB6 code into a VB.NET (or C#) project and compile it, I am supprised that you did not get more warnings and errors. As we developers know, one syntax error or misspelling could cause tens or hundreds of other errors, which means when you fix one, the others will disappear, too. Coding Horror implies that someone wrote horrible code. In this case, who that someone would be? The VB6 programmer or you? :)

My .NET Business Application Framework My Home Page

leppie

Xiangyang Liu wrote:

Coding Horror implies that someone wrote horrible code

Or that someone is experience a horror :)

Xiangyang Liu wrote:

If you copy VB6 code into a VB.NET

It was not copy. I used the converter in VS2005, which does a pretty good job, most of the forms actually open in the designer :) Most of the issues seem to be related to either missing libraries and interop stuff. The ActiveX bits and WinForms converted very well.

xacc.ide
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."

Pete OHanlon

Don't forget that most of those warnings will be in the form of, "this function doesn't exist anymore. You've got to write your own" types of warnings.

Deja View - the feeling that you've seen this post before.

RGSeeds

VB6 -> C# ... Does the converter fix all the optional parameters from the VB6 code? I've never used it myself :-O . If not you'll likely have a bunch of Type.Missing's to add

Vasudevan Deepak Kumar

leppie wrote:

so yes I am pushing for a fresh C# app

Good Move! Rather than suffering sick with the horrible VB! :mad:

Vasudevan Deepak Kumar Personal Homepage Tech Gossips