>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.
Yes. Under Win2K you're not supposed to put DLLs in the Windows folders.
>
>OK, I'm through whining, but I'd pay $$ to get the Setup Wizard back.
I saw on the newsgroups that someone was trying to get the setup wizard to work.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer