Technical information

General

wodAppUpdate component has two versions (both included in the package):

wodAppUpdateCom is a COM object (wodAppUp.dll), designed to be initialized dynamically from your code, and declared from within your code. It does not have user interface, it is windowless. Usually, you will initialize it with

and wodAppUpdate as ActiveX control (wodAppUp.ocx) - designed to be put on application's form using drag&drop from control toolbox. Once you put it on the form, no special code is required to initialize it, since your environment (usually VB) will handle it.

COM object licensing is not directly supported by any container. Unlike ActiveX controls which are licensed the moment you put them on the form (if you have licensed version of wodAppUpdate, of course), you need one more line to put in your code to license wodAppUpdate correctly:

Object information
Filename	wodAppUp.DLL (wodAppUp64.DLL for x64)
Class name	WeOnlyDo.wodAppUpdateCom.1
Class ID	{49A09BDC-BD7B-4669-B8C5-22005A62E847}
Events class ID	{0x5768B5A4,0xD345,0x4697,{0x9C,0x09,0x69,0x8F,0x2A,0xA7,0x5E,0x14}}
Compatibility	VB 5.0 and above, VFP 5.0 and above
Built with	Microsoft Visual Studio 2008 C++
Required DLLs	wininet.dll library

ActiveX Control information
Filename	wodAppUp.OCX (wodAppUp64.DLL for x64)
Class name	WeOnlyDo.wodAppUp.1
Class ID	{9E23E55F-3A26-4489-8734-EA83B13DD5DC}
Events class ID	{0x83EB366C,0x5E0C,0x418E,{0xA6,0x83,0x66,0xDF,0x64,0xAE,0x41,0x39}}
Compatibility	VB 5.0 and above, VFP 5.0 and above
Built with	Microsoft Visual Studio 2008 C++
Required DLLs	None required.

Interfaces
IUpdFile	{A9F435BC-0734-4CB2-BC97-E1001A3B9D77}
IUpdFiles	{C2F30F39-600A-477B-B05C-57788F6C1F28}
IUpdMessage	{40C94FC6-C109-460E-B425-91B068D2DC0D}
IUpdMessages	{805DA757-66E9-4F61-A079-5D4AE926E558}

Dosumentation
Help filename	wodAppUp.CHM

Distribution note

When you develop and distribute an application that uses this component:

1. Choose between COM object (wodAppUp.DLL/wodAppUp64.DLL) and the ActiveX control (wodAppUp.OCX/wodAppUp64.DLL) to include into the installation package. Both versions are independent on each other.

2. Above binaries can be included royalty-free in your application.

3. Use RegSvr32.EXE (or any other installer package creator) to register both the OCX and the DLL. Usually, installer software will do this for you

4. Install the component file(s) into the user's Windows SYSTEM32 folder. The component file(s) has/have version information built into it. So, during installation, you should ensure that you are not overwriting a newer version.

5. You should also distribute wodUpdS2.EXE service to remote system too if you want ability for wodAppUpdate to update files with no need for administrative privileges. When wodUpdS2.exe is distributed, you should install it by calling wodUpdS2 -i , and deinstall it by calling wodUpdS2 -u


Using licensed version

To use retail (licensed) version in your code, put your license key into LicenseKey property, immediately after initializing the component. For ActiveX control, you cannot do this (there is no LicenseKey property) because your license key will be read internally by wodAppUp.