BotDetect ASP.NET CAPTCHA Migration Guide

Upgrading BotDetect ASP.NET CAPTCHA from v2.0.9 to v2.0.10

Version 2.0.10 of the BotDetect ASP.NET CAPTCHA introduces several changes that require your attention when upgrading from older versions. For a detailed list of changes included in this release, please consult the related release notes.

All users

Since the Lanap.BotDetect.Captcha control output has been rewritten to produce semantic, tableless HTML, and most layout declarations have been moved to a separate CSS stylesheet, it is possible the Captcha control will fit differently inside your page layout (might be a few pixels off, etc). This is easily fixed by adjusting the CSS style declarations of your page.

Also, since the CAPTCHA code changing button has been added to the control and is enabled by default, you should, for example:

• Review how the control fits inside your page layout horizontally, if you don't have audio CAPTCHA enabled. The reload icon is rendered to the right of the CAPTCHA image.
• If you have audio CAPTCHA enabled and are using a CAPTCHA image height of less than 50 pixels, please review how does the reload icon fit inside your page layout vertically. If you need to show the reload icon to the right of the speaker icon (instead of below it), follow the horizontal icon layout instructions.

ASP.NET Ajax users

Since UpdatePanel compatibility is now added to the built-in Captcha control, the AjaxCaptcha workaround described in the UpdatePanel FAQ entry is no longer required. While this workaround will continue to work, it is now considered deprecated and it's recommended to stop using it. To do so, simply revert the changes used for the workaround.

Also, if you disabled the audio CAPTCHA inside an UpdatePanel because of Firefox compatibility issues, you can now enable it - this problem was caused by a bug in the Quicktime v7.1.6 plugin for Firefox, and is fixed in later versions of the player.

SharePoint users

Previous versions of BotDetect required minor source code modifications to change the CAPTCHA handler request extension, since SharePoint doesn't allow .aspx requests to map to a non-SharePoint HttpHandler. This can now be achieved with the official build of BotDetect, by specifying the prefered extension to use in the web.config file - for example:

<appSettings>
  <add key="LBD_RequestExtension" value=".ashx" />
</appSettings>
<web.config>
  <httpHandlers>
    <add verb="*" path="LanapCaptcha.ashx" 
      type="Lanap.BotDetect.CaptchaHandler, Lanap.BotDetect" />
  </httpHandlers>

will change the CAPTCHA sound and image request requests to use an .ashx extension. When using different extensions, don't forget to make sure they are mapped to the ASP.NET Runtime in the IIS properties for the website.

Also note that we have published instructions for creating a SharePoint Web Part with BotDetect CAPTCHA along with this update.