Create a utility that converts VB6 to VB.NET. That works!
Hardly anyone uses VB.Net now. Better to have a utility to convert VB.Net to the VB6 programming language.
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.
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 & ""
Ctr = Ctr + 1
If Ctr < 5 Then
For x = 1 To 25: DoEvents: Next
Laurie Stearn commented
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
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"
txtbatchno.Caption = s
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
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.
You have that the wrong way round.
The need is to migrate FROM dotNet.
To a lanuage like this one...
VB6 Programmimg Guide
The other way round would be better.
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...
@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.
Bring back VB6 programming now that VBdotNet is being abandoned.
What are the best alternative programming languages to dot net if you do decide to migrate away from VB6?
Better to convert FROM Vb.net to VB6 programming and VBA programming.
Real VB6 programming and VBA programming commented
There is no reason to convert from VB6 to VB.Net
Anthony D Green of Microsoft's Visual Basic Team says
"As for the product, VB6 applications are not being “dumped”. Per our support statement here: https://msdn.microsoft.com/en-us/vstudio/ms788708 we remain committed to “it just works” compatibility for existing VB6 applications through 2025."
Charles Hebbold commented
Support this suggestion to open source VB6:-
Zagor Tenay commented
When Microsoft tell you VB.Net has a long future ahead of it you realize it is about to be abandoned.
This is a post from the MS program manager for the VB team, Anthony Green, from January 2016:
Re: VB has a long future ahead of it no matter how you look at it. We're working on the next version – the 25<sup>th</sup> Anniversary version – VB15. Visual Basic is an open source language (check us out on github) so it can't really be killed even in the event of Mount St. Helens erupting and burying Microsoft campus in magma.
Update VB6 programming commented
Now that VB.Net is being abandoned this is no longer needed. What is needed is a tool to migrate to an updated VB6.
maurizio fichera commented
.net is a ******, vb6 was a winner.
Microsoft need to turn back to vb6 to create a new simply and powerfull compiler.