Is there a compelling reason why the IIsWebSiteHarvester creates a new IIsWebSiteHarvester object inside of the Harvest method instead of just calling this.HarvestWebSite? I've added some command line options to my IIs2KWebSiteHarvester and that threw me off for a minute; I looked at the DirectoryHarvester in order to figure out how to keep track of the parsed options.
I've added a server: option in order to harvest a web site off of a remote machine; does anyone else think this will be generally useful for the IIsWebSiteHarvester and RegistryHarvester extensions? Thanks, -- Thomas S. Trias Senior Developer Artizan Internet Services http://www.artizan.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
