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.
So right now I have project A and project B. Then there is a class library project Z. Project Z contains classes and methods both A and B use.
My question is, should I have project Z compiled and added to project A and B using its dll, or adding the project itself to both A and B?
Which cases would I use project in project in appose to dll in project?
If code from project Z is built and released on the same schedule as projects A and B, Z should probably be a part of the same solution.
On the other hand, if Z is a fairly stable library, with it’s own release/maintenance schedule, you’ll probably want to add it as a compiled reference.
You can ask yourself simple questions such as must Z to be compiled every time A and B are compiled? Should a developer working on A and B be able to modify Z?