Details on backward compatibility or migration to supported versions are provided below.įor specific details on the files included in each support group see the Runtime Definition section below. In some instances, later versions of these libraries are supported. This implies no warranties around support and servicing. These files are not supported on Windows instead they are subject to whatever support agreement applies to the media they were shipped with. Some files either have fallen out of mainstream support or were never included as a part of the runtime redist (e.g., they were included in the \Tools folder on the IDE media to support legacy VB4/VB5 applications, or they were third-party controls).
The supported version of the files is available online on the Microsoft Download Center ( ). The developer still needs to redistribute these files with the application. Typically, the VB6 IDE installed these controls to the developer machine by default.
This extended list consists of key controls, libraries, and tools that are installed from the IDE media or from to the developer machine. Supported runtime files –- Extended files to distribute with your application One key difference is that TriEdit.dll was removed from Windows Vista and later versions. These files have been tested for compatibility as part of our testing of Visual Basic 6.0 applications running on supported Windows versions.Īll supported Windows versions contain a nearly identical list of files, and the redist requirements for applications containing these files should be nearly identical. This lifetime is five years of mainstream support and five years of extended support from the time that a given version of Windows ships. Key Visual Basic 6.0 runtime files, used in the majority of application scenarios, are shipping in and supported for the lifetime of supported Windows versions.
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.
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:
The support policy below has been updated with Windows 10 version 20H2 support information.