I need to create a VS Setup and Deployment project that essentially
calls other setup programs.  I have heard mixed reviews about doing
something like this - including that this functionality was deprecated
after VS 2003.  I do have the current project calling a few other
setup programs right now, and it seems to work - what are some of the
issues and concerns i need to look into?

Also, I would like to add the other setup program's files into my
project - I don't want those files copied to the user's application
folder - i just want to run them directly. Currently, my custom action
adds the file to Application Folder then calls the exe.  I have
"exclude" property set to true so that the file doesn't show up after
install.  However, can i run the exe directly without copying it to
application folder?  This is particularly of concern if the setup
files are several gigs - i don't want to have to copy to the user's
machine then have to run it - i'd like to run it directly from the
distributed medium (e.g. CD ROM)

Finally, last question.  How would I include a set of files and
subdirectories to the project.  Right now, i can add files directly to
the application folder, but not directories.  Same thing applies as in
previous question -  i figure i can create a subdirectory and add it
in, but again i prefer not to have to copy the files to the user's
machine and take up extra space.

Thanks,

Ben