vb6 - Risks around relying on Visual Basic 6.0 applications -


given visual basic 6.0 runtime ships windows 7 , continue supported lifetime of os (until january 2020) , visual basic 6.0 ide, though no longer supported, stable, risks around keeping mission-critical applications in visual basic 6.0 next several years?

the official advice owners of vb6 apps microsoft uk is:

[do not upgrade or replace vb6 application if] application working great, has not required changes many years, there no plans extend functionality, nor need integrate newer applications

that tells factors increase risk vb6 application:

  • a need change application (bug fixes or new features).
  • a need integrate application newer applications.
    • but integration doesn't require migration. interop allows mix .net code vb6 (pdf whitepaper).

edit forgot mention main risk. migrating vb6 code .net can big task. in opinion it's easier in days: there excellent commercial tools; , more recent vb.net language features make easier. risk may become harder again if leave long. there come point when people ever going migrate have migrated: tools may disappear , community knowledge migration may degrade. /edit

i'm sure microsoft drop vb6 runtime, bear in mind windows 8 still supports 16-bit applications. , there's virtual machines. personally, think vb6 applications running long while yet.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -