>Hi Dragan,
>
>>Check Inno setup - I think that it doesn't have this problem. Its setups compress very well (dial it to the max, isn't much slower), the autoregistration of components is quite common, and it seems to handle the manifest stuff by itself. "Seems to", because I don't have the Vista to try it on, but then I have users who did, and they aren't complaining.
>
>Do you mean that Inno is able to build the manifest stuff ? So I can reuse the stuff ?
>
>Would be great. I indeed specifically need to get the "reg-free" com working. The full versions of installshield offers this. But I have no copy here and try to avoid bloatware...

From its help:
"OutputManifestFile=Setup-Manifest.txt

When this directive is set, the compiler will create a manifest file detailing information about the files compiled into Setup. The file will be created in the output directory unless a path is included."

i.e. it can create a manifest if you tell it to. Speaking of bloatware, I've seen a 200K .ise or .ism files lose tons and become 1-3K .iss script. Takes a few hours to learn - check the pages on Fox Wiki, there are good examples and reusable pieces, specially about runtimes.

http://www.jrsoftware.org/