>>FWIW I did once attempt to get around this by having the reference in one case to the project in the solution and in the other case to the actual DLL.
>
>Well, that certainly is an interesting way to solve that problem ... probably not recommended as a "best practice" though, huh? <g>

Absolutely not! I did however prove to myself that (a) it was doable and (b) I didn't want to do it....
Best,
Viv