Best approach for refactoring shared-library code to take into account dependencies?

Hi there

We've got a bunch of applications, and some common code. Each app has its
own subversion repository, as does each library of shared code.

If we want to refactor, I suppose we'll have to have one all-encompassing
solution that has all of the C# projects included into it, and do cross-project
refactoring with that...?

Are there other approaches?


1 comment
Comment actions Permalink

That is the only approach I'm aware of. I would suggest between subsystems you want pretty well defined apis so you don't have to do this. But within a body of code it isn't unusual to have different soutions for build, working on smaller subsystems, and an uber solution for refactoring.

Get that fast machine with mucho memory :>

I'b be curious if anyone else has another idea.



Please sign in to leave a comment.