BotDetect ASP Classic CAPTCHA Deployment Packages
The BotDetect ASP Classic Captcha component is distributed as a
.msi installation package. Both the free version available at the download page and the paid version available for purchase are packaged, used and deployed in the same way.
- Installation package contents
- Captcha COM component
- Captcha ASP library files
- Localization sound package files
- ASP code examples
- Deploying BotDetect updates
BotDetect ASP Classic CAPTCHA Installation Package Contents
The BotDetect ASP Classic Captcha installation package requires .NET framework 2.0, and supports all versions of IIS since 5.0 (included with Windows 2000).
By default, the BotDetect ASP Classic Captcha installs to
c:\Program Files (x86)\Captcha Inc\BotDetect 4 CAPTCHA Component\Asp\
CaptchaLibrary installation subfolder contains the Captcha ASP library files.
WebApp installation subfolder contains BotDetect demos and ASP code examples.
BotDetect ASP Classic CAPTCHA COM Component Deployment
ASP Captcha image and sound generation is performed by a special COM component (with the
BotDetect.Captcha.4 ProgID). Running the BotDetect installation package will automatically deploy and register the Captcha COM component, so you don't have to worry about the details.
In case you can't run the BotDetect installation package on your server, you can copy the
Redistribute\BotDetect.COM.dll file from a local installation to the server and follow the COM registration steps from the manual deployment guide.
BotDetect ASP Classic CAPTCHA ASP Library Deployment
When adding Captcha protection to your ASP Classic forms, you will need to copy Captcha ASP library files from the
CaptchaLibrary folder to your website source and include them on the form, as explained in the BotDetect Captcha ASP integration guide. You will then deploy these files together with your ASP application source.
BotDetect ASP Classic CAPTCHA Audio Localizations Deployment
BotDetect supports easy Captcha localization, but localized Captcha audio requires language-specific pronunciation sounds distributed as
.bdsp files. The
Redistribute\BotDetectSounds installation subfolder contains these files for North American locales, while pronunciation files for other locales can be downloaded from the Captcha localizations page.
Deploying these localized pronunciation files is as easy as copying the downloaded
.bdsp files for the locales you want to support to the
Redistribute\BotDetectSounds installation subfolder.
You can also use a different folder to keep
.bdsp files (in case you deployed the component without running the installation package, or if you want to keep them in version control together with your website source, etc.) You just have to specify the desired location in the
BotDetect/CaptchaConfig.asp file included in your application source, and make sure it can be read by the IIS worker process running your application.
BotDetect ASP Classic CAPTCHA Code Examples Deployment
The BotDetect ASP Captcha installation package also gives you the option to install a number of Captcha ASP Classic code examples. If IIS is enabled on the development machine, the samples will automatically be deployed and will be accessible from the BotDetect Start Menu folder (
Start → Programs → Captcha Inc → BotDetect 4 CAPTCHA Component → ASP → ASP Examples → Run), or by accessing
The BotDetect demos allow you to experiment with BotDetect options, while the code examples contain ASP Captcha sample code which might be useful when adding and configuring BotDetect Captcha protection on your ASP forms.
Typically, you will only deploy the BotDetect samples on your development machines, and skip them when installing BotDetect on your servers.
Deploying BotDetect ASP Classic CAPTCHA Updates
Running the updated setup package will automatically deploy the updated COM component, but you should stop IIS first for it to release all handles to the old DLL version. In case you deployed the old Captcha COM component manually, you will also have to remove it yourself.
New Captcha library files can usually just be copied over the old ones in your application source. If there are any version-specific instructions you should be aware of, they will be listed in the BotDetect ASP migration guide along with the new version release notes.