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.
Okay, so here’s the scenario.
Project A has a class library developed for it (lets call it MyLib). I release project A (in house project) with version 1 of MyLib.
I begin development on Project B, but expand MyLib to version 2, including a few optimizations to existing types.
If I release Mylib 2 to both Project A and Project B, I’m going to have to recompile Project A to support type changes, does anyone have solutions to this that are tried and true?
My suggestion: Continuous Integration.
Using a tool like CruiseControl.NET you could do a rebuild of every project/solution there is, even have the output of one (the .dll) uploaded to Source COntrol to be used by other projects, have unit tests run every time so you can check if additions / edits in a project used in solution A does not break Solution B also using that project. You could set the build to automatic every night or trigger one manually from the CruiseControl.NET systray app.