I suggest you ...

Create a utility that converts VB6 to VB.NET. That works!

243 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
William Peek shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

60 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    In this thread you'll only find old programmers who refuse to accept any other programming language than vb6.

  • Microsoft, update VB6 programming & VBA programming commented  ·   ·  Flag as inappropriate

    No need to convert VB6 to VB.Net. VB6 programming is still supported by Microsoft.

    Here is Microsoft's support statement for VB6 programming...

    Support Statement for Visual Basic 6.0 on Windows
    - (updated with Windows 10 version 1709 support information).

    The Visual Basic team is committed to "It Just Works" compatibility for Visual Basic 6.0 applications on the following supported Windows operating systems:
    Windows 10
    Windows 8.1
    Windows 7
    Windows Server 2016
    Windows Server 2012 including R2
    Windows Server 2008 including R2

    The Visual Basic team’s goal is that Visual Basic 6.0 applications continue to run on supported Windows versions.
    As detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions, which is five years of mainstream support followed by five years of extended support.

    The VB6 runtime will ship and will be supported in Windows 10 for the lifetime of the OS (that is until at least 2025).
    The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS (that is until at least 2027).

    https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy

  • rodriques commented  ·   ·  Flag as inappropriate

    To be honest. VB.NET does not have any projects since just a very few programmers use this also-called "language".

    VB6 is used fully today and new projects are made in VB6, not in VB.NET.

  • rodriques commented  ·   ·  Flag as inappropriate

    Now VB.Net is being abandoned we must have a utility to convert to VB6.

    No one is going to use VB.NET software. If it didn't happen 15 years ago, it won't happen now.
    The rules that applied then apply now. Companies do not pay to rewrite all their applications in the BAD and IRRELEVANT technology which does NOT function any longer.
    And VB.NET applications generally run slower. It makes no sense.

    VB6 is fast, fastest than C++. Only a developer living in an idealistic fantasy world thinks that and asked to make app's in VB.NET.
    Some posters here have no knowledge or experience to understand why legacy applications SHOULD work between variants. The latest and unpopular technology, like NET is just that, unused, unpopular, no matter how hard MS wants that. There are fundamental reasons why everyone is still talking about Visual Basic 6.0.

    Notions of how organizations operate will not change that. All companies use VB6.

  • Daniel commented  ·   ·  Flag as inappropriate

    avid user of vb6 like me is suggesting not only in vb.net but also to the other languages and vice versa, so many languages now a days but vb6 is the best, maybe updating this that can convert to any languages much better.. ty very much

  • Anonymous commented  ·   ·  Flag as inappropriate

    Hardly anyone uses VB.Net now. Better to have a utility to convert VB.Net to the VB6 programming language.

  • Microsoft, update VB6 programming & VBA programming commented  ·   ·  Flag as inappropriate

    This is no longer needed.

    As detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions, which is five years of mainstream support followed by five years of extended support

    The VB6 runtime will ship and will be supported in Windows 10 for the lifetime of the OS.

    The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS.

    https://docs.microsoft.com/en-us/dotnet/visual-basic/reference/vb6-support

  • Anonymous commented  ·   ·  Flag as inappropriate

    If CMS_Data_Ado.State = 1 Then CMS_Data_Ado.Close
    On Error GoTo file_use_err
    '----------------For RDO Connectio
    '---------------------For ADO connection----------------
    Ctr = 0
    CMS_Data_Ado.Provider = "sqloledb"
    'ConnStr = "Server=DATA_SERVER;Database=CMS_data;Trusted_Connection=yes"
    ConnStr = "Data Source=" & CMS_Data_source & ";Initial Catalog=" & CMS_Initial_catalog & ";user Id=" & CMS_User_Id & ";Password=" & CMS_Password & ""
    CMS_Data_Ado.Open ConnStr

    Exit Sub

    file_use_err:
    Ctr = Ctr + 1
    If Ctr < 5 Then
    For x = 1 To 25: DoEvents: Next
    Resume
    End If
    MsgBox (Error$)
    End

  • Laurie Stearn commented  ·   ·  Flag as inappropriate

    TBQH we have been told many times it cannot be done, yet to bring such a utility to more than 80% or more of total reliability is something no-one has resource or time for it seems.
    Or do we? If MS could make the 2008 conversion utility _itself_ open source on a .git repository then anyone can have a go. Then if we can't make a better job of it, then there is no reason to blame MS any more for it. Is there?
    Unless, after all is said and not done, MS do decide to revamp VB6. :P

  • Ali commented  ·   ·  Flag as inappropriate

    Dim b As Byte() = Nothing
    b = StrConv(dtm, vbUnicode)

    s = ""
    For i = 0 To Information.UBound(b)
    f = Strings.Chr(b(i))
    If f = 0 Then
    s = s + "A"
    ElseIf f = 1 Then
    s = s + "B"
    ElseIf f = 2 Then
    s = s + "C"
    ElseIf f = 3 Then
    s = s + "D"
    ElseIf f = 4 Then
    s = s + "E"
    ElseIf f = 5 Then
    s = s + "F"
    ElseIf f = 6 Then
    s = s + "G"
    ElseIf f = 7 Then
    s = s + "H"
    ElseIf f = 8 Then
    s = s + "I"
    ElseIf f = 9 Then
    s = s + "J"
    End If
    Next
    txtbatchno.Caption = s

  • Lofaday - 0AV com - new IDE abandoned commented  ·   ·  Flag as inappropriate

    Happy new year all! Let's see if this idea has got legs.. See www.vb64.com and please comment..

    Basically it's a wrapper to MS VB6 itself providing a replacement IDE GUI and integrated hashing "TransCompiler" (source-to-source compiler) for both VB6's compiler (which, if you don't have already, you need to get seperately from MS .. details on vb64 site).

    By modernising and adding features to the IDE itself, and yet by legitimately using VB6's compiler, we can offer TOTAL VB6 COMPATIBILITY and add some integrated extras (like COM zip, jpeg saving, code management). Better still, the "TransCompiler" offers a roadmap to different platforms. OS's, etc -- and secures your skills for the future.

    The main purpose is to legitimize VB6's ongoing use, by being able to say to your clients "it is current and it is supported". I will need your help though to kickstart it! :-)

  • ARM brings back VB6 programming commented  ·   ·  Flag as inappropriate

    No need for this now that VB6 programming will run on ARM processors under full Windows 10.

    You'll even be able to run the VB6 IDE on an ARM tablet.

    dotNet will be too slow on ARM processors, so a great future for VB6.

  • Sathiamurthi commented  ·   ·  Flag as inappropriate

    Use RAD tool to convert basic structure of VB to target language.. I prefer PHP angular js...you can save cost as it is open source and quickly migrate...

  • Erel commented  ·   ·  Flag as inappropriate

    @sam check the B4X suite: https://www.b4x.com

    A RAD tool based on vb language (not identical) that supports: Android, iOS, desktops, servers, Raspberry Pi, Arduino and more.

  • paul commented  ·   ·  Flag as inappropriate

    Bring back VB6 programming now that VBdotNet is being abandoned.

← Previous 1 3

Feedback and Knowledge Base