DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 11 of 11

Thread: Upgrade Wizard Poll

  1. #1
    Patrick Troughton Guest

    Upgrade Wizard Poll


    I've got a question and I was hoping to get some honest feedback. This question
    is for anyone who's tried to upgrade an existing VB6 project to VB.NET using
    the Upgrade Wizard.... I

    f you've used the Upgrade Wizard, you probably know that there are somethings
    it upgrades just fine, and other things it can't handle as well. My question
    is, of the things it can't handle well, what are the biggest stumbling blocks?
    IOW, what doesn't it upgrade that you wished it did?

    You can list as many items as you want. But please limit them to things the
    Upgrade Wizard doesn't handle. For example, I realize that some people are
    passionate about Wend=>End While but this is something the Upgrade Wizard
    handles just fine. I'm interested in hearing about the things it doesn't
    upgrade, the ones that are most important to you. If you haven't used the
    Upgrade Wizard, please don't respond, this is for people who have actually
    used it.

    Thanks!

    /Pat
    --------------------------
    It's the platform, stupid.
    --------------------------

  2. #2
    Gary Nelson Guest

    Re: Upgrade Wizard Poll

    > f you've used the Upgrade Wizard, you probably know that there are
    somethings
    > it upgrades just fine, and other things it can't handle as well. My

    question
    > is, of the things it can't handle well, what are the biggest stumbling

    blocks?
    > IOW, what doesn't it upgrade that you wished it did?


    I've got a lot of (old) functions where I haven't dimed all of the
    variables. In my opinion the wizard should be able to do the following:

    VB6 Code:
    Sub MySub
    for x% = 1 to 100

    next
    End Sub

    Vb.Net Code:
    Sub MySub
    Dim x as short
    For x = 1 to 100

    next
    End sub

    Right now the wizard dims x as an object even though it is followed by a %.
    The same goes for #, &, $, !, etc.

    Gary





  3. #3
    Kent Guest

    Re: Upgrade Wizard Poll


    M$ is well aware of it's limitations. If they cared at all they would have
    provided a good migration path before releasing VB.Net. They don't care
    about VB developers and they never will.

    There is no need for you to do their market research for them.

    "Patrick Troughton" <Patrick@Troughton.com> wrote:
    >
    >I've got a question and I was hoping to get some honest feedback. This question
    >is for anyone who's tried to upgrade an existing VB6 project to VB.NET using
    >the Upgrade Wizard.... I
    >
    >f you've used the Upgrade Wizard, you probably know that there are somethings
    >it upgrades just fine, and other things it can't handle as well. My question
    >is, of the things it can't handle well, what are the biggest stumbling blocks?
    >IOW, what doesn't it upgrade that you wished it did?
    >
    >You can list as many items as you want. But please limit them to things

    the
    >Upgrade Wizard doesn't handle. For example, I realize that some people are
    >passionate about Wend=>End While but this is something the Upgrade Wizard
    >handles just fine. I'm interested in hearing about the things it doesn't
    >upgrade, the ones that are most important to you. If you haven't used the
    >Upgrade Wizard, please don't respond, this is for people who have actually
    >used it.
    >
    >Thanks!
    >
    >/Pat
    >--------------------------
    >It's the platform, stupid.
    >--------------------------



  4. #4
    Dave Guest

    Re: Upgrade Wizard Poll


    "Patrick Troughton" <Patrick@Troughton.com> wrote:
    >
    >I've got a question and I was hoping to get some honest feedback. This question
    >is for anyone who's tried to upgrade an existing VB6 project to VB.NET using
    >the Upgrade Wizard.... I
    >
    >f you've used the Upgrade Wizard, you probably know that there are somethings
    >it upgrades just fine, and other things it can't handle as well. My question
    >is, of the things it can't handle well, what are the biggest stumbling blocks?
    >IOW, what doesn't it upgrade that you wished it did?
    >
    >You can list as many items as you want. But please limit them to things

    the
    >Upgrade Wizard doesn't handle. For example, I realize that some people are
    >passionate about Wend=>End While but this is something the Upgrade Wizard
    >handles just fine. I'm interested in hearing about the things it doesn't
    >upgrade, the ones that are most important to you. If you haven't used the
    >Upgrade Wizard, please don't respond, this is for people who have actually
    >used it.
    >
    >Thanks!
    >
    >/Pat
    >--------------------------
    >It's the platform, stupid.
    >--------------------------


    1. Control arrays: These are easy for me to modify to true dynamic control
    creation in my VB6 projects prior to running the upgrade wizard, so I'm mystified
    why the upgrade wizard doesn't do something similar instead of creating the
    abortion it does for these.

    2. Proper conversion of 'App' object methods: The upgrade wizard picks the
    most long-winded .NET equivalent for these, which I then promptly change
    to the more concise version after upgrading. E.g, why doesn't the wizard
    convert "App.ProductName" to "Application.ProductName"? (instead it converts
    to "System.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecuting Assembly.Location).ProductName").

    3. Collection enumerators: why does the wizard ask us to explicitly uncomment
    the line to get these working? This drives me nuts since I don't usually
    remember to do this until I see my code breaking.





  5. #5
    Gary Nelson Guest

    Re: Upgrade Wizard Poll

    Sheldon,

    > (By the way, *what* have they done now that int is 32 bit???
    > Does the upgrade wizard update that too?).


    Well, it won't fix the name of the variable, but it will change:

    Dim x as integer

    to

    Dim x as short

    Gary



  6. #6
    Gary Nelson Guest

    Re: Upgrade Wizard Poll

    Sheldon,

    > No, that would be:
    >
    > Dim intX as integer
    >
    > to
    >
    > Dim intX as short
    >
    > So "intX" is a short, its naming convention notwithstanding.
    > Hungarian is the one to beat!


    Right, that's what I meant to say. It won't correct the int in the name but
    it will change the dim.

    Gary



  7. #7
    Sheldon Rosenfeld Guest

    Re: Upgrade Wizard Poll


    Strange, I thought that only *I* was the contrarian by using the
    suffixes.
    It's so much fun to read the professional opinions in the ng's
    that deride the lousy coding standards of those foolish
    enough to utilize them.
    Ya see, *professional* coders use Hungarian prefixes of
    int, str,instead of suffixes %, $.
    (By the way, *what* have they done now that int is 32 bit???
    Does the upgrade wizard update that too?).

    Sheldon

    --------------------------
    It's the stupid platform
    --------------------------

    "Gary Nelson" <gn@contanet.es> wrote in message
    news:3e3e6080@tnews.web.devx.com...
    > > f you've used the Upgrade Wizard, you probably know that there are

    > somethings
    > > it upgrades just fine, and other things it can't handle as well. My

    > question
    > > is, of the things it can't handle well, what are the biggest stumbling

    > blocks?
    > > IOW, what doesn't it upgrade that you wished it did?

    >
    > I've got a lot of (old) functions where I haven't dimed all of the
    > variables. In my opinion the wizard should be able to do the following:
    >
    > VB6 Code:
    > Sub MySub
    > for x% = 1 to 100
    >
    > next
    > End Sub
    >
    > Vb.Net Code:
    > Sub MySub
    > Dim x as short
    > For x = 1 to 100
    >
    > next
    > End sub
    >
    > Right now the wizard dims x as an object even though it is followed by a

    %.
    > The same goes for #, &, $, !, etc.
    >
    > Gary
    >
    >
    >
    >




  8. #8
    Sheldon Rosenfeld Guest

    Re: Upgrade Wizard Poll


    No, that would be:

    Dim intX as integer

    to

    Dim intX as short

    So "intX" is a short, its naming convention notwithstanding.
    Hungarian is the one to beat!

    BTW, no criticism here, just inquiring...

    Sheldon


    "Gary Nelson" <gn@contanet.es> wrote in message
    news:3e3e9c21$1@tnews.web.devx.com...
    > Sheldon,
    >
    > > (By the way, *what* have they done now that int is 32 bit???
    > > Does the upgrade wizard update that too?).

    >
    > Well, it won't fix the name of the variable, but it will change:
    >
    > Dim x as integer
    >
    > to
    >
    > Dim x as short
    >
    > Gary
    >
    >




  9. #9
    Guest

    Re: Upgrade Wizard Poll

    1) APIs

    2) Structures (especially with Fixed-Length Strings, since the ByValTStr
    truncates the last char, replacing with a null)

    3) In fact, all code with FLS

    4) User Controls (and I use a lot of them, though I've found most have a
    simpler substitute using inheritance)

    5) Custom Collections

    and

    6) The translated code is really very poor .NET code

    I'll bet there are many more, but because of 6) I simply gave up on it and
    whatever I'm doing in .NET, I'm doing from scratch.


    PS: This doen't mean I don't like .NET, in fact I'm very found of it. But
    VB6->VB.NET migration path is simply non-existing.

    Miguel Santos



  10. #10
    Guest

    Re: Upgrade Wizard Poll

    Oh and

    7) All code using the Printer object. Because I've build my own printing
    platform in VB6 this in not too bad, I'll 'only' have to rewrite the engine.
    But this is giving me quite a few headaches because of the completly
    different model.

    Miguel Santos



  11. #11
    Patrick Troughton Guest

    Re: Upgrade Wizard Poll


    Hi Gary,

    I ran your code through the Upgrade Wizard in VB.NET 2003 Final Beta. I gave
    it this....

    Sub MySub()
    Dim s$
    Dim a%
    Dim b#
    Dim c&
    Dim d$
    Dim e!

    For x% = 1 To 100
    Next
    End Sub

    ...and the updated Upgrade Wizard converted it into...

    Sub MySub()
    Dim s As String
    Dim a As Short
    Dim b As Double
    Dim c As Integer
    Dim d As String
    Dim e As Single

    Dim x As Short
    For x = 1 To 100
    Next
    End Sub

    /Pat
    --------------------------
    It's the platform, stupid.
    --------------------------

    "Gary Nelson" <gn@contanet.es> wrote:
    >> f you've used the Upgrade Wizard, you probably know that there are

    >somethings
    >> it upgrades just fine, and other things it can't handle as well. My

    >question
    >> is, of the things it can't handle well, what are the biggest stumbling

    >blocks?
    >> IOW, what doesn't it upgrade that you wished it did?

    >
    >I've got a lot of (old) functions where I haven't dimed all of the
    >variables. In my opinion the wizard should be able to do the following:
    >
    >VB6 Code:
    >Sub MySub
    >for x% = 1 to 100
    >
    >next
    >End Sub
    >
    >Vb.Net Code:
    >Sub MySub
    >Dim x as short
    >For x = 1 to 100
    >
    >next
    >End sub
    >
    >Right now the wizard dims x as an object even though it is followed by a

    %.
    >The same goes for #, &, $, !, etc.
    >
    >Gary



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center