Sep 24, 2010 07:17 PM|mbanavige|LINK
the script shouldn't be able to resolve any additional paths by checking IIsWebDirectory too
The IISWebDirectory cannot itself be fully processed. But, its child objects might be relevant...
The script (v3) does not process (or recurse through) the IISWebDirectory class object so it would miss any nested IIsWebVirtualDir paths.
It's not essential that an IISWebDirectory itself be directly processed per se, but it is essential that all child objects of that IISWebDirectory be included in the scan - in case they happen to be of class IIsWebVirtualDir.
I do see that the script download has changed a bit and now links to a v31 script. But the v31 script behaves the same as the v3 script in this regard from what i can tell.
Note: the newer v31 script did pick up one extra path that even my modified older v3 script did not. It was an IIsWebVirtualDir on my dev system that did not have a web.config at all.