Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve got a solution with two projects, A and B. A references an external dll C.dll from an external /lib folder.
When I build B, C.dll is ending up in its /bin folder.
B does not reference A or C.dll (but A does reference B).
There is no mention (reference) to/of C.dll anywhere in project B, why is it in its /bin? How can I determine where its coming from?
Update: Using .NET 3.5
Thanks
If you build your solution on the command line with MSBuild and increase the verbosity you can figure it out. You can just execute the following in a Visual Studio Command Prompt (found in the Start Menu under Visual Studio).
This will create write the log file
msbuild.login the current directory. Then you can search for the file name and back track how it is being copied into that directory. Ifv=diagis too much info you can tryv=detailed.