Hi, Mark!
Thanks for your reply. I've found this article (although the trailing dot in URL confused my explorer

Problem is that it is the end user, that discovers the erroneous setup. If SF asks for .vbp file I expected that at least first level dependencies had been taken into account. So my question was rather "why?". Why SF didn't include some DLL's, that were presented in the same Reference section of .vbp, as others. The only difference that I see is the path - these DLL's are in Designers subdir of Common Files.
Is there any decision, or the only way is to manually compare .vbp and .dep with the list of included files for every VB setup?
Thanks in advance.
Regards,
Gennady
[This message has been edited by gena (edited 01-16-2001).]
Leave a comment: