This is ironic, considering that the basic design of .NET is based upon making copies of all dependent DLLs in the local build directory of each project. I have a solution with 25 web service projects that is generating a 90MB MSI file which would be less than 10% of that size if duplicate files weren't being stored!
Is there any way to prevent this?
How could MS leave out such an important feature?
Isn't the effort to implement this very small?
Apparently, most .NET applications of moderate size or larger using standard MSI files to install are generating MSIs that are much larger than they should be, thus taking longer to generate, download, copy, install, etc. Good grief.
Is this an evil plot to drive users to other products?
