Hi Diego,

Steps to produce the error? Just visiting the page causes the error?

I'm not getting any error on my local machine nor on the demo site.

Did you use the new Web.config file?

Does Web.config file have this at the top:

<sectionGroup name="system.web">
      <section name="sanitizer" requirePermission="false" type="AjaxControlToolkit.Sanitizer.ProviderSanitizerSection, AjaxControlToolkit" />
    </sectionGroup>

and this lower down in the file:

<sanitizer defaultProvider="HtmlAgilityPackSanitizerProvider">
        <providers>
          <add name="HtmlAgilityPackSanitizerProvider" type="AjaxControlToolkit.Sanitizer.HtmlAgilityPackSanitizerProvider" />
        </providers>
      </sanitizer>

I have both of those on my local machine and get no errors but I notice on our demo site I apparently did not use the new Web.config so those items are not there, and still no such error on the demo site.

I would say if you don't have that in Web.config then try adding it, but if you do have that then try commenting it out or removing it and see if that makes a difference.

If you remove it from the top make sure you keep this part:

<sectionGroup name="system.web"></sectionGroup>

Hope that helps,

Joe

Hi Diego,

I was able to produce this error on my local machine and I seem to have found a solution.

Change this:

<sanitizer defaultProvider="HtmlAgilityPackSanitizerProvider">
        <providers>
          <add name="HtmlAgilityPackSanitizerProvider" type="AjaxControlToolkit.Sanitizer.HtmlAgilityPackSanitizerProvider" />
        </providers>
      </sanitizer>

to this:

<sanitizer defaultProvider="HtmlAgilityPackSanitizerProvider">
        <providers>
          <add name="HtmlAgilityPackSanitizerProvider" type="AjaxControlToolkit.Sanitizer.HtmlAgilityPackSanitizerProvider, SanitizerProviders" />
        </providers>
      </sanitizer>

and uncomment this in the <tagMapping>:

<add tagType="System.Web.UI.ScriptManager" mappedTagType="AjaxControlToolkit.ToolkitScriptManager" />

Hope that helps,

Joe

I'm still battling through this problem. The fix I mentioned before seems to have uncovered another problem in the toolkit where the ajaxrating is broken, it will crash the page if the page has rating enabled on anything after making the change that fixes the other problem.

I really hate the ajaxcontroltoolkit, I need to be working on something else but yet again this thing is giving me headaches and making me work on this problem instead of what I need to be working on.

The worst part is that Microsoft seems to have washed their hands of any obligation to fix this thing, now DevExpress is supposed to be maintaining it but so far no-one has made any new release with any fixes for this turd.

I may have to go back to the previous version of the toolkit wew were using and then make a new release again if I can't figure out a solution to this.

Never once have I had a good experience updating to a new version of the ajaxcontroltoolkit, and this current one has been out since Dec 2013, and its been badly broken all this time

Wow, okay, thanks Joe. I'll wait until you have stabilized all of the Ajax features you're using, then figure out how I need to deploy it to production. I don't think using debug=true would be too big of a problem--I know I've run in production with this set in the past (accidentally, since that's the default setting in the delivered web.config) and didn't have any adverse affects or performance issues that I could see.

Jamie

Ouch! Okay, Joe, thanks for the update.