Hi,

I am trying integrate the clickonce deployment with our automatic build process, but I am having a problem with copying all the references to the output directory. I can better illustrate with an example.

Project 1 (Startup Project)
---references:
-------Project 2 assembly reference
-------AReference.dll

Project 2
---references:
-------1.dll - installed in GAC
-------2.dll - installed in GAC
-------3.dll

Using the clickonce deployment built in to Visual Studio 2005, I can go to the properties of Project 1->Publish-> Application Files and see a list of all the references, including those that are currently in the GAC. Also inside Visual Studio, I have the option to include these files (meaning that it wil copy them for deployment. If I publish Project 1, the manifest will have information about 1.dll, 2.dll, and 3.dll, as well as AReference.dll. How does the Application Files feature in Visual Studio determine, and copy those files? That is exactly what I would like to do from the autobuild process.

If it is not possible to determine the dependencies, like the publish->application files feature can do, getting those files to copy to the output directory would work as well, which leads me to question 2. How do I get the references in project 2, into the output directory of project 1 (project 1 is the main project)? I can get those references in project 2's output directory, but I need them to be in project 1's.

Any help would be greatly, greatly appreciated!

Thanks,

Ryan

Well,

I wasn't able to get it to work like I wanted, but by using msbuild I was able to copy the files that I needed to the correct directory. It turned out that the files I needed were 3rd party extensions that could be copied from an externalLib directory that we have.

Ryan