I see a lot of samples where people add a Visual Studio project containing all the references that are used on all the other projects in the solution.
An example is KandaAlpha . Watch for KandaAlpha.References.
Why should I do that?
Share
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 see a lot of samples where people add a Visual Studio project containing all the references that are used on all the other projects in the solution.
An example is KandaAlpha . Watch for KandaAlpha.References.
Why should I do that?
It’s probably to ensure that all dlls are included in the output folder. I’ve seen that technique with plugin archetectures that use reflection to load plugin assemblies. You reference all the needed dll’s in one project and then reference that project from the main project. That will pull in all the dll’s that were referenced from the first project.