>>Pretty simple, really. We break up our install into multiple scripts, and dispatch them based on SDDialogs fired in our main script. Each subordinate script is uninstallable in and of itself as an individual component.
>
>Ah, gotcha. Good idea.
>
>>Frankly, we've been playing around with the Setup API and Windows Scripting Host - it's likely that we'll start rolling our own installers using the facilities built into the operating system!
>
>That's the way it should be. I loathe InstallShield (and WISE has some severe drawbacks), so I just may look into this option myself. Would I have everything I need to mess with this with VS?

You'll want to have the Platform SDK as well, whch can be downloaded from MS if you don't have an MSDN subscription. The API and scripting host stuff are pretty thoroughly documented in the MSDN on-line docs (basically the same as the docs that came with VS Enterprise). We've found that Scripting Host scripts and some custom apps do a great job; the Setup API handles the component upgrade/update issues pretty well, and anything we can't get at with automation objects has been doable in VB or VFP with API calls.