I have created a DLL which resides in a shared folder on our IIS server. When comsumed from this location, the DLL is automatically copied to the BIN folder of the consuming project. The DLL is eventually copied to the production location when the consuming project is published to the production server and everything works as expected. So, of course, it now has to be changed!

My manager doesn't want the DLL referenced from the shared folder on the IIS server. He thinks a project ought to be able to to reference a DLL from within the TFS Source Control folder associated with the project creating it. The issue has to do with restoring our IIS server in the case of some catastrophic event wiping out our entire server room; simply backing up the IIS server is evidently more painful than recompiling everything? Mine is not to wonder why...

So, I've included the DLL in the project creating it, checked it into TFS and the DLL now appears in the Source Control folder as expected. I tried browsing to the TFS source folder in the Add References dialog box, but it doesn't appear to recognize the path provided (\\tfs server name\collection name\source control folder\...\BIN\name.dll.) Nor can I seem to open the soruce control folder in Windows Explorer.

Any sites I've Googled suggest using a shared folder as I mentioned above, and do not even mention referencing DLLs within TFS. Does it seem likely the issue is that I simply haven't constructed the path correctly, a security problem (we do NOT manage the TFS server and probably do not currently have rights to access it outside of TFS), or is it just not possible to browse to a TFS source control file oustside of the Source Control Explorer (possibly because it's in some database and not in DOS?) IOW, is this even possible? If so, how?