I tried adding it as an application under the main site and pointed to the relevant directory and after the usual fun and games (usually needing to add permissions for
> tag around system.web and system.webserver elements in the parent site's web config.This indeed stops the inheritance but then I had a follow-on problem with a 500.22 error which detects an invalid config setting for integrated pipeline mode. This is a strange error since all I added was a (valid) location tag but then found another post here: http://runtingsproper.blogspot.co.uk/2010/04/solved-iis7-validateintegratedmodeconfi.html which describes the workaround as removing any httphandlers from the system.web section. I don't know why this only happens with the location tag, perhaps the invalid code is ignored if the config is inherited (since it might be inherited into a classic application pool?) but anyway, in my case, I didn't need the module so I simply removed it and the site came back to life.