1) You have a version of "X" (1.0) installed in the GAC
2) You have a new version of "X" (2.0).
3) You add the X.2.0 DLL's to a folder in your solution
4) You add references to the X.2.0 DLL's to your project
5) You check the solution in.

6) Another developer, open's his project up and syncs (not yet having
X.2.0)
7) The solution comes down but because the X.2.0 DLL's come down after
the project that references them the IDE repoints your references to
the 1.X.0 DLL's.

8) There is nothing you can do to overcome this issue, <codebase>
<probe> whatever has no effect because the IDE said use 1.X.0, sigh
......

Hi Mike,

Yeah, IDE is totally dumb when it comes down to side by side issues.
It looks only for assembly name and doesn't care about versions and other
kinky stuff.

--
Miha Markic - RightHand .NET consulting & software development
miha at rthand com

"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 1) You have a version of "X" (1.0) installed in the GAC
> 2) You have a new version of "X" (2.0).
> 3) You add the X.2.0 DLL's to a folder in your solution
> 4) You add references to the X.2.0 DLL's to your project
> 5) You check the solution in.
>
> 6) Another developer, open's his project up and syncs (not yet having
> X.2.0)
> 7) The solution comes down but because the X.2.0 DLL's come down after
> the project that references them the IDE repoints your references to
> the 1.X.0 DLL's.
>
> 8) There is nothing you can do to overcome this issue, <codebase>
> <probe> whatever has no effect because the IDE said use 1.X.0, sigh
> .....