Supported runtime files - Shipping in the OS The runtime is divided into the three groups:
Examples of these files include the Visual Basic 6.0 runtime library ( msvbvm60.dll), controls (i.e., msflxgrd.ocx) along with runtime support files for other major functional areas (i.e. These files were marked as distributable in the original Visual Basic 6.0 license. The Visual Basic 6.0 runtime is defined as the compiled binary files originally included in the redistribution list for Visual Basic 6.0. This announcement does not change the support policy for the IDE.
Additionally, both the Windows and Visual Basic teams have tested Visual Basic 6.0 IDE on Windows Vista, Windows 7, Windows Server 2008, Windows 8, and Windows 8.1 to understand and mitigate (if appropriate) compatibility issues on 32-bit versions of Windows (see the 64-Bit Windows section below for further information about 64-bit systems). The Visual Basic 6.0 IDE is no longer supported as of April 8, 2008. Visual Basic 6.0 Runtime Extended Files: selected ActiveX control OCX files, libraries, and tools shipping with the IDE media and as an online release.Visual Basic 6.0 Runtime: the base libraries and execution engine used to run VB 6.0 applications.Visual Basic 6.0 IDE (Integrated Development Environment).Visual Basic 6.0 is made up of these key deliverables: For additional information and product documentation, see the Visual Basic 6.0 Resource Center. The support bar will be limited to serious regressions and critical security issues for existing applications.
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 Visual Basic team’s goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. The Visual Basic team is committed to "It Just Works" compatibility for Visual Basic 6.0 applications on the following supported Windows operating systems:
Why not do the same in windows? A little structure wouldn't hurt.The support policy below has been updated with Windows 10 version 20H2 support information. Back in the good old days when I was using Amiga computers (RIP) at least there was a folder called libraries in the system drawer. I would like to take this opportunity to complain a little about the windows directory: it's a mess! How the *%#! did MS come up with the idea "let's put all library files in the windows/system drawer! And everything else too!".
I could ship all nesessary files with my program, but that would mean an increase of the filesize from 30k to at least 600k! I have provided a link where you can download the latest runtime files on my homepage, I hope thats enough for people to get my program started. I'm using the latest version of MS Visual Basic 6, the problem is most often on the users side, not having the latest versions of all libraries. I was just trying to help you get my program started. Problems with different version of dll:s and ocx:s is a common problem. I am just trying to keep the 'incredibly confusing windows directory' under control.) If I like it, I'll post it on my Freeware site!(Please don't take this e-mail out of context. :) I'll let you know how your rename app works. I know it's not easy working with other peoples 'limited' files, but maybe your just not using the right programming language? Anyway, telling me to back up my current OCX file was very thoughtful. I check my system regularly for conflicting files as I have found numerous errors associated with them. People might have problems if and when Microsoft releases a new version of the same file. But I should warn you that putting your own version of a Microsoft file into circulation may not be a good idea.