C# deploy dependency files?

I need to deploy a project that uses an API. That API has a series of dependent DLLs (about a dozen). I use ClickOnce to deploy my apps. I'm trying to figure out the best way to build my project, include the dependencies and still use ClickOnce.

1. I think post-build script(s) migh开发者_如何学Got make the most sense for this. Is there another way to do this?

2. Some of my users will need the new API functionality, others will not. Is there a way to include the dependency files in one build and not another? For example, I want "Debug" to include the API dependencies while "Release" should not.

You can add all the dependencies as references to the project, they will then get deployed with it.

You will not be able to have separate files with this method, however.