AjaxControlToolKit debug or Release mode?

This is a quickie, just some fast need to know information. . .

If you've experienced slow page results with AjaxControlToolKit enabled pages and have double-checked your pages are not running in debug mode plus you've made sure the web.config for your application isn't running in debug mode...But what else?

Well I could kick myself for not noticing this, but fortunately Adi in the asp.net forums woke me up.

When you build the AjaxControlToolKit solution in Visual Studio check to make sure you're building in Release mode.
By default the binaries that are created with the build will be debug versions unless you make the change.

Once you install the AjaxControlToolKit you'll have 6 folders under it.
After you Build the Solution you'll have either Debug or Release versions of the binaries located in:

\AjaxControlToolkit\AjaxControlToolkit\bin\Debug
\AjaxControlToolkit\AjaxControlToolkit\bin\Release

and...

\AjaxControlToolkit\SampleWebSite\Bin

and...

\AjaxControlToolkit\ToolkitTests\Bin

Currently the Debug and Release file sizes are:
AjaxControlToolkit.dll (Debug) 1,212 KB
AjaxControlToolkit.dll (Release) 1,192 KB

For the production version of your AjaxControlToolKit enabled application replace the AjaxControlToolkit.dll Debug binary with the Release version and you should see a speed increase.

  Salute,
    Mark Wisecarver

Share this post:                                       
Published Wednesday, February 07, 2007 10:01 PM by wisemx

Comments

No Comments