Ajax.Config = Site Collection Feature?

Feb 22, 2008 at 12:52 PM
Hi guys,

The Ajax.Config feature is a feature that is scoped to Site Collection level. Wouldn't it make more sense to scope it to the Web Application level? Every Web Application can have more than one Site Collection. So Site Collections share the same web.config. It doesn't make sense to have the feature active for Site Collection A and deactivated for Site Collection B if they both share the same web.config. Maybe this will cause even some issues when deactivating the feature on a site collection while another site collection in the same web application still makes use of it?

Do you agree or am I totally wrong?? :-)

Feb 24, 2008 at 9:06 PM
Makes sense to me
Mar 22, 2008 at 11:43 AM
is this feature going to be upgrade somehow? Or is one expected to do this oneself ? ;-)
it would be nice to:
- have it scoped to web-application
- remove it correctly from web.config after "deactivate" (i have the impression that it doesnt remove enough)

grtz, Tom
Mar 27, 2008 at 10:19 AM
I can't remember who contributed it :-), but I'll look into it