Edited Unassigned: ToolkitScriptManager/CombineScriptsHandler requires registration system.web/httpHandlers [27592]

According to documentation (http://www.asp.net/ajaxLibrary/AjaxControlToolkitSampleSite/ToolkitScriptManager/ToolkitScriptManager.aspx) I must register CombineScriptHandler using following code
```
<system.web>
<httpHandlers>
<!-- Using CombineCriptsHandler.axd as path of handler -->
<add verb="*" path="CombineScriptsHandler.axd"
type="AjaxControlToolkit.CombineScriptsHandler,
AjaxControlToolkit" />
</httpHandlers>
</system.web>

<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
<handlers>
<!-- Using CombineCriptsHandler as name of handler -->
<add name="CombineScriptsHandler" verb="*"
path="CombineScriptsHandler.axd"
type="AjaxControlToolkit.CombineScriptsHandler,
AjaxControlToolkit" />
</handlers>
</system.webServer>
```
Specifically, the handler must be registered twice - in system.web/httpHandlers and in system.webServer/handlers. Using system.web/httpHandlers requires system.webServer/validation/@validateIntegratedModeConfiguration to be set to false.
This is really bad practice becase AjaxContrlToolkit requires me to use IIS6-style handler registration which is now obsolete and no longer supported, I I must tell IIS7 to ignore that obsolete way of registration (instead of throwing an exception).

I found workaround: Instead of polluting my web.config with obsotele IIS6-style handler registration I can set CombineScriptsHandlerUrl (in OnInit of my ToolkitScriptManager-derived class). But the property is obsolete and generates warning in C# compilation, which is also not good.

It would be good to either un-obsolete the CombineScriptsHandlerUrl property or remove the requirement to register the handler in IIS6's system.web/httpHandlers.