Last post Mar 06, 2014 02:01 AM by Happy Chen - MSFT
Feb 28, 2014 06:32 AM|dieseldave|LINK
There are many posts on various forums that state that you need to add a couple lines to your web config to avoid this error. MOst refer to the
Yet that appears to have been replaced by another sanitizer called - HTMLAgilityPack. I have that and a sanitizers dll in my bin but nno mater how I have tried adding the suggested references to the config file I get this error, or the sanitizer reference
in the config file is underlined as an error. Does any one know how to configure this to work?
Mar 02, 2014 09:19 PM|Happy Chen - MSFT|LINK
I don't know if this will be your problem, but I encountered this when I didn't have the following section（system.web） in my web.config :
<add name="AntiXssSanitizerProvider" type="AjaxControlToolkit.Sanitizer.AntiXssSanitizerProvider"></add>
You'll also need to have this in your configsections:
<section name="sanitizer" requirePermission="false"
type="AjaxControlToolkit.Sanitizer.ProviderSanitizerSection, AjaxControlToolkit" />
please check out the link for details:
Ajax Control Toolkit July 2011 Release and the New HTML Editor Extender
Hope it helps you.
Mar 05, 2014 01:42 PM|dieseldave|LINK
the provider you referece is supposedly outdated. It ha s been replaced with HTMLAgilityCOntrol but that errors when you try to put it in the web.config. Anyway, I just went back to the old Editor.
Mar 06, 2014 02:01 AM|Happy Chen - MSFT|LINK
if so ,could you provide any additional code or markup related to this issue?
It may be a bit easier to resolve if it can be easily reproduced.
Thank you for your understanding.