It appears that following my conversion to .NET 2 some of my dependent assemblies aren't getting copied accross more than one level.

i.e.MyRemoteBusinessServices references MyDataAccessObject that references both MyBusinessObjectPersistenceMappingAU and MyBusinessObjectPersistenceMappingUK.

MyBusinessObjectPersistenceMappingAU.dll and MyBusinessObjectPersistenceMappingUK.dll are not being copied to ..\MyRemoteBusinessServices\bin\Debug.

These are getting built into ..\MyDataAccessObject\bin\Debug but not copied accross to the remote business services binary area. The MyBusinessObjectPersistenceMappingAU and MyBusinessObjectPersistenceMappingUK projects do not have any managed code, they are just performing persistence mapping between properties and the Db.

If I create a dummy class in one of these projects and reference it in the MyDataAccessObject project then the assembly is copied all the way down. It looks like VS2005 is trying to do some new sort of compiling where it checks if assembly functionality is implemented before it copies the dependency accross. Is there a way that I can turn this off so I dont have to have this dummy class implementation??