Solving the Installation Problem

Make no mistake -- there is no simple "fix" to the problem of safely distributing Visual Basic applications. However, if you have complete information about the incompatibilities that occur and the versions of both components and VB executables, it is possible to quickly determine exactly what problems exist. Once you have this information, it becomes easy to find the correct solution.

VersionStamper allows you to easily embed into your Visual Basic executable or other OLE container information about all of the dynamic link libraries and custom controls used by that application, along with required current versions, file date and time, and your choice of warning conditions. The VersionStamper ActiveX control or component can use this information to check the versions of the actual modules that are available on the target system.

dwvstp??.ocx -- The 16 and 32 bit ActiveX control includes extensive dialog box support for embedding version information for selected DLLs, OCXs, VBXs and other files. Each control can embed two file lists so you can use a single control to create dual platform executables. It also has the ability to scan Visual Basic -based projects to automatically create a list of DLLs, OCXs, and VBXs required by the application. The ActiveX version even allows you to scan for files not specified in your file list during run-time.

The run-time distributable control is royalty free. These controls are fully compatible with Visual Basic 4.0, 5.0, 6.0, and other true ActiveX Control containers!

VersionStamper 6.5 is also capable of reading file lists off of an Internet/Intranet web or ftp site so that your end user can verify that they are using the very latest components!

If you are still working with Visual Basic 3.0:

The first, and most obvious need is to embed a standard Windows version resource into executables created by Visual Basic. This will make it possible for any standard Windows installation program to correctly handle your Visual Basic programs and prevent the accidental overwriting of later versions of your executables.

VersionStamper contains the dwvstamp.vbx custom control which makes the process of embedding a version resource into your executable completely automatic. The version information is entered by setting the control's properties at design time just as you would set the properties for any custom control. This information will be converted into a standard version resource automatically during the compilation process.

Solving the Distribution Problem

The key to eliminating problems relating to the distribution of Visual Basic applications is to be able to determine, quickly, whether all of the components required by the application are, in fact, present in the runtime environment.

Embedding Component Version Information into your Application
The VersionStamper control makes it possible to embed into the executable a complete list of every DLL, VBX or other software component that is needed by your program. This embedded component information includes the required version information for each component. You can also specify the conditions under which a warning will be triggered. This information can also be saved in an external file or on a web or ftp site for VersionStamper to scan.

VersionStamper includes an advanced Dependency Wizard that is able to automatically scan a Visual Basic project for a list of the custom controls used by the program and a list of all DLLs referenced by the Declare statements in the project. This Wizard also has the ability to determine indirect dependencies -- DLL's or OCX's that depend on other dynamic link libraries, and is able to monitor a running application for modules loaded by that application.

Detecting component incompatibilities at runtime
Since an executable stamped by VersionStamper "knows" exactly what components it requires at runtime, it is an easy matter for it to check if all of those components are available and up to date. This comparison process is also built into the VersionStamper custom control.

VersionStamper provides a great deal of flexibility in terms of how you handle the scanning and reporting process. Beginning programmers may simply choose to add the standard Vervrfy.frm form or vervrfy2.frm form and associated modules to their application to provide a default verification check at load time or under user control.

The ActiveX edition even allows you to scan for files not specified in your file list during run-time. The run-time distributable control is royalty free.

These controls are fully compatible with Visual Basic 4.0, 5.0, 6.0, and other true ActiveX Control containers!

More advanced programmers may choose to modify the code to create their own custom report. You might also provide the user with a step-by-step procedure on how to fix certain problems, or perhaps a request that they call your customer support line.

It is possible for the software components required by an application to be so old that the program will not run at all. For these cases VersionStamper includes two sample "Rescue" programs which are able to compare the component requirements of an executable with the runtime environment without actually loading that executable. One of the rescue programs include complete Visual Basic source code and can be fully customized to suit your own needs.

Make your application "self-repair"
What happens when VersionStamper discovers and incompatible or obsolete component? With version 6.5, VersionStamper adds the ability to automatically download and install the updated component from an FTP site over the Internet or corporate Intranet!

Additional Tools and Information

VersionStamper 6.5 includes a new program called VsWizard.exe which is able to scan a running application, standalone binary file, or Visual Basic project and determine the list of dependent files used. With this information, it can then create a VersionStamper Script file which can be read by the VersionStamper control to find conflicting files.

VersionStamper also includes a program called VerInfo.exe which is able to report on the version information of any executable that contains a version resource. It is also able to report on the embedded component information added by the VersionStamper custom control.

This program also includes full source code. Which brings us to one of the final features of this package, a feature that we feel is one of the most important.

Some additional features of VersionStamper are:

VerResQ.exe -- A Visual Basic-based program that analyzes any Visual Basic-based executable stamped by VersionStamper. It instantly detects any incompatibilities that exist between the requested files and those actually present on disk. Includes source code so that it can be customized for distribution with your application.

VerSplsh -- This sample project demonstrates using a standalone executable to perform file verification for your main application. It displays a splash screen during file verification. If no conflicts were found, it Shells your application, otherwise a form is displayed notifying the user of the conflicts. This method will allow you to identify any incompatibilities that exist -- even if the executable cannot be loaded. Designed to be easily modified so that you can create your own splash screen shell program to distribute with your application.

VsRTDemo -- This sample project demonstrates how to scan files dynamically during run-time.

VsWebLst -- This sample project demonstrates how to retrieve a VersionStamper Script File from a web site and use the file information from the script file to verify files during run-time.

AutoUpdate -- Similar to VsWebLst, but will also automatically replace conflicting files by downloading them from a pre-determined ftp site and installing them to the target system.

Technical Notes -- include a complete discussion of the Windows-based system of version stamping and the embedding techniques used by VersionStamper. It also includes detailed suggestions and examples for improving the Visual Basic setup toolkit. It also includes an extensive discussion of platform dependent issues including Windows 95, Windows 98, and Windows NT.

But fear not -- this product was designed to be used by absolute beginners as well. And for those who just need a quick solution to the distribution problems discussed earlier, feel free to skip forward to the Quick Start section which will walk you through the process of embedding component information and adding a runtime conflict report (and embedding a version resource for VB 3.0) in a few easy steps.