At some point Microsoft (who no longer support the IDE) will also stop supporting the VB runtime, and companies will have no choice but to convert those old apps.
I doubt if there will ever be a VB6 revival.
I think they should focus on 100% compatibility, and 64bit code generation.
Perhaps allow the new Apps to connect to modern cloud services instead of MS access, or on premises SQL, preferably without anyone having to touch any code.
Also some kind of project analysis and auto-documentation so the new developers can understand what the project does, would be useful.
>I think they should focus on 100% compatibility, and 64bit code generation.
100% compatibility seems to be the main focus of the twinBASIC developers.
64bit code is already available. One big issue is ActiveXs - they are supported, but there are few 64bit third-party ActiveXs. So the support of 32bit ActiveXs in 64bit twinBASIC apps is planned but not yet available.
I doubt if there will ever be a VB6 revival.
I think they should focus on 100% compatibility, and 64bit code generation.
Perhaps allow the new Apps to connect to modern cloud services instead of MS access, or on premises SQL, preferably without anyone having to touch any code.
Also some kind of project analysis and auto-documentation so the new developers can understand what the project does, would be useful.