>Here's a basic question:
>I have a solution that contains 5 projects.
>All 5 projects reference a dll - wsgutilitieslib.dll that contains many utilities used by this solution but is not a project in the solution.
>wsgutilitieslib.dll rarely changes, but it does occasionally.
>What should I do in the calling solution when I make changes to wsgutilitieslib.dll?
>I've been removing and re-adding the reference to it in each project of the solution.
>Is that necessary? Is so, it's getting to be quite a pain.
>What's the most efficient way to handle something like this?

As Viv mentioned, this should be automatic. In my case, I have Framework.dll added as a reference to all projects. Once I compiled Framework.dll, I only have to compile the project and a new copy of Framework.dll will be copied in the Bin directory of the local project.

I do however have a specific situation that if I compile the Framework project too many times, while it remains opened, this could create a lost reference in one or many client projects which are opened. When that happened, I simply close the client project and reopen it and the reference is back ok. However, there has been a thread about it recently. You might want to check it out.