>>>>>>HI
>>>>>>
>>>>>>I'm looking at a .NET project which contains references to several external dlls.
>>>>>>
>>>>>>I want to move the project but when I do it cabn't find the dlls any more as the refernces to the dlls have changed and are pointing to an invalid location.
>>>>>>
>>>>>>What am I doing wrong.
>>>>>>
>>>>>>Thanks
>>>>>>
>>>>>>Nick
>>>>>
>>>>>I see Viv answered. I've fixed quite a few of these same situations. If you can't find a specific DLL, check the bin folder of the production site. I usually create a "Library" folder in the root of my app that contain all the external DLL's and those get checked into source control with the app. This makes the source code portable. IMO, you should be able to pull down the source from source control and build it immediately without having to tinker around with it.
>>>>
>>>>Hi,
>>>>I alway dither about this issue. But, in the approach you suggest above, do you really need the 'Library' folder. I think it would work if you put the DLLs directly into the /bin folder, turned off 'Copy Local' and referenced them there ? Of course whilst the upside of this approach is that you know you will always get the same DLL version the downside is that you will not neccessarily get the latest version :-}
>>>
>>>I don't include the bin folders in source control.
>>But you could do so - instead of the 'Library Folder'
>>> Also, I have multiple projects in most of my solutions that use the same .dlls, so this gives me a one-stop shop.
>>OK - that makes sense. But then why put the 'Library' folder in the root of one of them rather than completely seperately ? Doesn't source control for other apps get confused ?
>
>I meant the solution root, not the project root.

Gotcha . Thx.