-
-
General
wodWebServer component has two versions (both included in
the package):
wodWebServerCom is a COM object (wodWebD.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
- Dim WithEvents WebServer1 as
wodWebServerCom
and wodWebServer as ActiveX control (wodWebD.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 wodWebServer, of course), you need one more line
to put in your code to license wodWebServer correctly:
-
- WebServer1.LicenseKey =
"put.your.key.here"
-
| Filename |
wodWebD.DLL (wodWebD64.DLL for
x64) |
| Class
name |
WeOnlyDo.wodWebServerCom.1 |
| Class ID |
{F83384B7-851A-42B5-A5A7-C99801CBD830} |
| Events class
ID |
{0xC5993E49,0xA536,0x4179,{0xAF,0xF3,0xD2,0x4D,0xE8,0x94,0x76,0x57}} |
|
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
| Built
with |
MS VC++ 6, PSDK,
OpenSSL |
| Required
DLLs |
None required,
wodCertificate.dll optional, only if Certificate and
Key generation/loading/saving is used. |
-
| Filename |
wodWebD.OCX (wodWebD64.OCX for
x64) |
| Class
name |
WeOnlyDo.wodWebServer.1 |
| Class ID |
{BAE03663-41EA-459D-BD2C-69284762233F} |
| Events class
ID |
{0x3C131A71,0x98FB,0x4F46,{0xAC,0xC5,0xD8,0x5E,0x43,0xFA,0xE9,0x35}} |
|
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
| Built
with |
MS VC++ 6, PSDK,
OpenSSL |
| Required
DLLs |
None required,
wodCertificate.dll optional, only if Certificate and
Key generation/loading/saving is used. |
-
|
IISAPIExtension |
{67C086BE-DF96-426F-A4F7-E83641CDFEFE} |
|
IISAPIExtensions |
{0C9012AD-BB36-4F76-8C8C-A9E661C5E2DF} |
|
IWebHeader |
{131191D3-2464-4E8A-9F61-811B6BC7D464} |
|
IWebHeaders |
{21FD76C4-E187-4F32-B8D2-0C2D428B282F} |
|
IWebRequest |
{7EE45962-6662-4CF6-BA00-04E87861B3E9} |
|
IWebRequestUploadPart |
{BE1F8DC6-B9A5-46E3-B3A9-E612FD104AE7} |
|
IWebRequestUploads |
{662A898C-9F66-4FFC-84B9-800C3B3B9CF2} |
|
IWebResponse |
{9CDDBBC4-42BE-419B-9EA3-762EC303B31C} |
|
IWebSession |
{709EF4D1-CE29-47A2-8C08-96F82F27E60E} |
|
IWebSessions |
{91E33933-AFFE-4347-BED2-BB948212A440} |
| IWebUser |
{47EA9049-627A-4B5B-9D4F-75F0CBCB3010} |
| IWebUsers |
{BB60E22D-71B5-41D4-B3BD-020047CA08E4} |
|
IwodWebNotify |
{6FA1059E-15BF-462e-BFC6-3BB985BA55FA} |
-
| Help
filename |
wodWebD.CHM |
Distribution note
When you develop and distribute an application that uses
this component:
1. Choose between COM object (wodWebD.DLL/wodWebD64.DLL) and the ActiveX
control (wodWebD.OCX/wodWebD64.OCX) to include into the installation
package. Both versions are independent on each other.
2. You should include wodCertificate.DLL/wodCertificate64.DLL for Certificate
management - if it is needed in your application.
wodWebServer does not depend on it - only uses it for
client authentication with the private key and the
certificate ( suitable for HTTPS protocol ).
3. Above binaries can be included royalty-free in your
application.
4. 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
5. 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.
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 wodWebServer.
|
