>I would have thought that including the runtime libraries in the Install Shield build would have included >all< necessary runtime files. Short of telepathy (and folks like you!) what's a harried developer to do?
>
>Actually, I never saw the VC runtime as an option while building the install -- but then I wasn't specifically looking for it either. So far, I'm not terribly impressed with Install Shield. For the majority of things I do, it's too complicated and quite cumbersome. I can see where some features would useful for vertical market apps. I particularly disliked the handlling of destination directories (would anyone really install a DLL in "c:\program files\your company name\default"?) and of the registry (I don't really want to mess with registry keys: just register the file properly as 6.0 used to do.) In short, it seemed like I was using a pile-driver to place a push-pin.
>
>OK, I'm through whining, but I'd pay $$ to get the Setup Wizard back.

Lynda,


Mike made some very good points, but let me add one thing about the installation of DLLs. From my knowledge of how Win2K works, you'd definitely want to copy the run-times to the local directory. For one thing, Win2K is extreemely protective of its system directory. For another, it allows side-by-side DLLs. All of this was implemented so that folks like you and I wouldn't be caught up in "DLL Hell".

What I'd say you're suffering from is a case of "Oh no! Not another piece of software to learn!" syndrome. While I haven't worked with it extensively, I'd say that just about anything would be an improvement over the Set-up wizard.