>It depends what the linker pulls into the DLL/EXE in terms of external references. Some framework/extensions can be statically linked (MFC for example) and it can be a little tricky to determine what comes with an OS and what doesn't. After you have performed your build process run the DUMPBIN utility using the /DEPENDENTS option, this allows you to see the DLL's that are statically linked and those that are delay/runtime loaded (you could also use the dependency walker to do this).
>
>To see what you should deploy in terms of runtimes its always a good idea to cross reference this against the compiler/SDK/API documentation, just type redistribute in the MSDN index page and see what you get.
>
>If you are redistributing using a large media format (CD-ROM) then include all your versions used for development. If you use a good installer all the versioning issues should be transparent to you as long as the DLL's/runtimes have a version resource embedded in them.
>
>HTH
>Neil


Thanks Neil.