|
|
leppie wrote: I have been given a VB6 project to upgrade to C#
Bah, that's nothing. Or null. Or empty.
[ 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
|
|
|
|
|
Surely this is better than being given a C# app to downgrade to VB6? And better than being given a VB 6 to maintain.
|
|
|
|
|
Better that than the other way round
|
|
|
|
|
That's was a pretty big typo there ^^
Nice Rule btw
-------------------------------
Carrier Bags - 21st Century Tumbleweed.
|
|
|
|
|
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?
|
|
|
|
|
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."
|
|
|
|
|
leppie wrote: so yes I am pushing for a fresh C# app
Good Move! Rather than suffering sick with the horrible VB!
|
|
|
|
|
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?
|
|
|
|
|
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."
|
|
|
|
|
VB6 -> C# ... Does the converter fix all the optional parameters from the VB6 code? I've never used it myself .
If not you'll likely have a bunch of Type.Missing's to add
|
|
|
|
|
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.
|
|
|
|
|
Now this[^] is something you don't see in an application very often. I wonder why?
|
|
|
|
|
I like your screen size estimate. Puts things in perspective very nicely.
|
|
|
|
|
In terms of 3 dimensional CGI views, what kind of perspective do you need to view 400m of backdrop?
Lousy joke really. I ought to give up... So should he...
Ninja (the Nerd)
Confused? You will be...
|
|
|
|
|
Good comemnt on the screen size. As I read the thread, I was thinking what monitor even has 25000 pixels across it's width. A 50 inch monitor would need a pixel width of 50 microns in order to accomadate that.
|
|
|
|
|
Yeah, even if the columns were a single pixel wide, the grid still extend over 21 feet. Now that's useful!
|
|
|
|
|
So what we need now is one of:
- much bigger monitors;
- horizontal outlining;
- line wrap (and maybe taller monitors).
Luc Pattyn [Forum Guidelines] [My Articles]
this months tips:
- use PRE tags to preserve formatting when showing multi-line code snippets
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
...and if the user looks at 1 cell per second, it would take almost 7 hours
to view the data for 1 row..if he can get it to scroll that fast
Sweet.
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I was only able to get 24,348 columns, he'll never be able to make it 25,000. It's impossible.
Seriously though, could you imagine trying to come up with 25,000 column headers? I can just imagine the person trying to read the data and remember a column value that was 10,000 columns behind where they currently scrolled.
My next question, is this a web app? Can you imagine that amount of data over a healthy 56k line.
|
|
|
|
|
It is just one of those things people come up with to justify their quest for a new
and bigger machine ...
Luc Pattyn [Forum Guidelines] [My Articles]
this months tips:
- use PRE tags to preserve formatting when showing multi-line code snippets
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
Chris Kowalske wrote: Can you imagine that amount of data over a healthy 56k line
Sure, he'd just have to come back and check it next month to see if it has loaded
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
Ya, now think about all the times you've seen a healthy 56k line (0 for me).
|
|
|
|
|
Chris Kowalske wrote: think about all the times you've seen a healthy 56k line (0 for me).
Must have been some years ago. I have not used dial-up for about 6 years now
"Find it your bloody self - immediately!" - Dave Kreskowiak
|
|
|
|
|
Chris Kowalske wrote: Seriously though, could you imagine trying to come up with 25,000 column headers?
No need to have unique Headers: That would be like "Peak No. 523, Signal/Noise Ratio".
Ist not nonsensical to display the Info at all. Its his attempt to press them in one flat table.
Only Database-specialists would even think of something like that...
Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal. George Orwell, "Keep the Aspidistra Flying", Opening words
|
|
|
|