>>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.

I think thats a good idea Mike.
I've taken on a new bit of work and I'm trying to find the neatest way to set it up. Both for my convenience and for when I've gone.

The project is pulling in several dlls from different software suppliers which have been installed on other development machines so when I tried to rebuild the project quite a bit was missing.

NIck

Nick