VersionStamper について

エンド・ユーザーのシステムで起こり得るコンポーネントバージョン非互換性を検出し管理できます。

VersionStamper はどんなプロジェクトについてでもコンポーネント依存性を決定して、埋め込み、あるいはリモートファイルリストに基づいた競合を検出して、そしてソフトウェアアップデートの自動的な通知を行ないます。完全なアプリケーション配布ソリューションです。アプリケーションによって使われるコンポーネントのすべてを決定して、そして自動的に検証しリモートアップデートするためのスクリプトを作成するのに役立つ依存性ウイザードも含みます。

What's New in V6.5

  • Batch mode support for generating your reference file list.
  • Support for scanning Wise and InstallShield installation script files.
  • Custom Message support for script files that allows you to dynamically display additional information on a file conflict.
  • Now includes the full SpyWorks WinSock component that supports HTTP file retrieval and proxy servers.

What's New in V6.0 (New features apply only to the ATL VersionStamper control)

Properties

  • FoundDateHigh - Supercedes the FoundDate property, uses new Windows Date format
  • FoundDateLow - Supercedes the FoundDate property, uses new Windows Date format
  • FoundGUID - Returns GUID string of the file. Refer to the GUID Format for more information
  • FoundTypeLibLCID - Returns LCID value of the file. Refer to the GUID Format for more information
  • FoundTypeLibVersion - Returns typelib version string of the file. Refer to the GUID Format for more information
  • FoundVersionString - Returns the File Version string resource of the file. This is not the same as the FoundVersion property which returns a string representation of the File Version number
  • OtherDateHigh - Supercedes the OtherDate property, uses new Windows Date format
  • OtherDateLow - Supercedes the OtherDate property, uses new Windows Date format
  • PathRefFileName - Valid only for files that has the Path Override option set to "Reference File". Contains the file name of the reference file whose directory is used to search for this file
  • RefDateHigh - Supercedes the RefDate property, uses new Windows Date format
  • RefDateLow - Supercedes the RefDate property, uses new Windows Date format
  • RefGUID - Returns GUID string of the file. Refer to the GUID Format for more information
  • RefTypeLibLCID - Returns LCID value of the file. Refer to the GUID Format for more information
  • RefTypeLibVersion - Returns typelib version string of the file. Refer to the GUID Format for more information
  • RefVersionString - Returns the File Version string resource of the file. This is not the same as the RefVersion property which returns a string representation of the File Version number
  • ApplicationName - Name of the executable (including extension) performing a conflict check for used to check the "AppPath " registry entry which changes the default Windows search pattern. Normally not used unless your application supports this registry entry. This property is also referred to during a VerifyObjectFile method call. After setting the EXE name, you can retrieve any special paths that Windows will search in for this application by retrieving the property value
  • UserDirectory - User-defined path in which to also check for a particular file. Valid only when a "relative user-defined directory" search is specified. Ignored if directory does not exist

Events

  • FileScan Event - This event has several changes. A new parameter name PathFlags contains a Long value that specifies special path overrides used to search for this file. The StopScan parameter has been changed from an Integer to a Boolean. The VerifyFlags parameter also supports new flags now. For more information refer to the FileScan Event
  • FileConflict Event - This event's Flags parameter supports additional flags now. For more information refer to the FileConflict Event

VerScan - The new dwvsob36.dll file included in VersionStamper 6.0 is a new ActiveX component that actually contains the file verification engine used by VersionStamper. It also exposes a VerScan object that can be used instead of the VersionStamper control. This is useful when creating formless applications, or when you do not need to add another ActiveX control to your application. For more information refer to the VerScan object.

Run Time Verification - The new VerifyObjectFile2 method call supercedes the previous VerifyObjectFile and includes support for the new enhancements and path overrides. The VerifyObjectFile method still exists for backwards compatibility. For more information refer to the VerScan object.

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 OLE custom control can use this information to check the versions of the actual modules that are available on the target system. Incompatibilities are instantly detected! VersionStamper is able to automatically scan a 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. VersionStamper has the ability to determine indirect dependencies - DLL's or OCX's that depend on other dynamic link libraries. VersionStamper also adds new support for the Internet and corporate intranets. Now you can keep an updated list of file dependencies on your Web or FTP site that your application can be programmed to check. If it finds a problem or updated file, it can notify the user, send Email back to your company, or even have VersionStamper automatically download the correct components from your web or FTP site. It is also useful for corporate IS departments who can now be sure that their clients really do have the right components on their system - before tying up the service desk for hours

VersionStamper is designed with your needs in mind. You can perform version verification automatically on load, or at any time you wish under program control, or even dynamically verify a list of files at run time. Plus, a customizable and redistributable "rescue" program can be used to detect and log problems when an application won't load at all. VersionStamper is designed primarily for DLLs, ActiveXs, and VBXs, but will work with any type of file, even those without embedded version information.