@ William, correct, the entire assembly will be added.
It concerns me that deployment footprint optimizations are the first thing some people seem to want to do. Unless it is needed, you are just creating more work for yourself than needed. Yes, if you NEED to shrink the size of the deployment, copy the source files you NEED directly into you own project.
This goes against just about every software development best practice there is (code duplication typically = bad code smell), but yes you can do that if you want. Not sure why you would waste your time and customers money by copying it out and re-testing it all (as you would need/should to do for a commercial release) unless absolutely necessary. Then next month when a fix comes out, you need to find the details of the fix, and incorporate that into the version that you copied out - which may be 3 or 4 versions old, and re-test everything again. Oh and you need to do that fix across all the projects you copied the code into. Yuck.
So to save a couple of KB in deployment footprint, at consultant rates, you have cost the client an additional couple of thousand dollars in effort at a minimum, added time to the delivery schedule, and given yourself a future headache since you are now the owner of the code and responsible to update it to incorporate any fixes / optimizations others, or your client finds.
Lets not forget that .NET has the concept of assemblies/libraries for a reason, to promote reuse, encapsulation and separation of concerns between components. If you copy everything into one assembly you loose those benefits and your code will become a maintenance nightmare.
I’m not saying never copy code into you own project, but it shouldn’t be the first thing you do, and you should have a (good) reason behind it. My 2c