We have several external DLL files being referenced in our Web Application Project. We have a deployment project for installing on the hosting servers. When we were using .N
Something weird had happened to my deployment project. When I saw it had no detected dependencies, I removed the primary output and re-added it.
The dependencies are now showing up and being placed in the bin folder when installed.
We can use the <Private>False</Private>
to not to copy the referenced DLL files to the bin
directory. This is useful when we are building applications in a separate TFS build server where we need to build the application and not to copy the DLL files to the bin
directory.