>>>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?
>>
>>AFAIK, if you add a reference to an external DLL in a project it will always use the current (i.e. latest) version. No special action neccessary. Do you have a situation where this is not the case ?
>
>Viv
>No, I don't have a situation where it's not the case, but for some reason, I thought I had to do that.
>So if I just build the solution, I'll be OK?

I think so. All I can say is that I've never seen a problem with that approach....