|
-
Jun 19th, 2004, 03:52 PM
#1
Thread Starter
Addicted Member
BIG can of worms?????
I think I just opened up a BIG can of worms from some information gained from a variety of these forums. Not counting hundreds of small programs, I have several large programs developed in vb6 over the years. They have been stable for a long time but periodically, they need minor changes and/or additions.
Recently I concluded I will be needing some of the features of VB .net in the relatively near future. Last night I went out and purchased the Visual Basic .net Standard edition and installed it on my system. Then I pulled out one of my bigger programs to "convert" it like the book says.
I won't even guess how many error messages I encountered. Most of them however, are directly related to VB6 and constants. For example:
1. I need to color code a lot of fields for specific use on different forms and use vbBlue, vbYellow, vbWhite, etc.
2. I use many custom procedures to display/print information on the screen and to the printer. Therefore, to save lines of code, I declare a global variable (prnWhere) that I send to all print routines. The print routine then selects the printer.scalemode such as vbTwips or vbCharacters.
3. And others.
None of these converted.
At this point, I have decided NOT to convert most of the programs until such time as it is required. However, the one that just threw up on me is the primary reason I bought VB .net int the first place.
Any advice?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|