BotDetect ASP.NET CAPTCHA API Reference

First Time Here?

Check the BotDetect Developer Crash Course for key integration steps.

Table of Contents

BotDetect.Web ASP.NET CAPTCHA Reference

The BotDetect.Web namespace contains BotDetect classes encapsulating Captcha web-related functionality, and used within the System.Web context.

BotDetect.Web.UI ASP.NET CAPTCHA Reference

The BotDetect.Web.UI namespace contains BotDetect controls used within ASP.NET Web Forms applications (equivalent to System.Web.UI).

BotDetect.Web.Mvc ASP.NET CAPTCHA Reference

The BotDetect.Web.UI.Mvc namespace encapsulates BotDetect types specific to ASP.NET MVC Captcha implementations. It's separated from the main BotDetect assembly into BotDetect.Web.Mvc.dll so referencing BotDetect doesn't cause a dependency on ASP.NET MVC (unless BotDetect.Web.UI.Mvc.dll is also referenced).

BotDetect ASP.NET CAPTCHA Client-Side Reference

BotDetect client-side functionality is encapsulated in the bdc-script-include.js JavaScript include. BotDetect Captcha controls automatically use this library and construct the necessary objects.

BotDetect ASP.NET CAPTCHA Core API Reference

While the BotDetect.Web members are used for Captcha control functionality within a Web context, the root BotDetect namespace contains members related to general Captcha functionality, independent of the context it's used for.

BotDetect ASP.NET CAPTCHA Enumerations Reference

A number of enumerations is used to represent basic Captcha options available in BotDetect.

BotDetect ASP.NET CAPTCHA Events Reference

BotDetect uses a number of Captcha-specific events to allow detailed tracking of all phases in the Captcha workflow.

BotDetect.Configuration ASP.NET CAPTCHA Reference

BotDetect exposes a configuration facade over the underlying configuration implementation reading BotDetect settings from .NET .config files.

BotDetect.Logging ASP.NET CAPTCHA Reference

BotDetect logging functionality is now encapsulated in the BotDetect.Logging namespace, making custom logging provider implementations much simpler.

The BotDetect logging provider using log4net is separated from the main BotDetect assembly so referencing BotDetect doesn't cause a log4net dependency (unless BotDetect.Troubleshooting.dll is also referenced).