I´m working on a project, in Visual Studio 2008, which DLL currently surpasses 20 MB. Is there a way to profile that DLL, searching the main contributors to this size?
I suspect that breaking it in smaller projects inside the solution would help, but I’m looking for a faster solution (although not better, I’m afraid).
As a sidenote, we are getting ‘unexpected error writing metadata’ error, that we think it’s related to the DLL size. However, when restarting Visual Studio 2008, the error vanishes. Until it appears later again, after a few rebuilds. The disk space is not a problem.
Yowser! Have you perchance got some huge resx files (or other embedded content) that are getting embedded in the dll? Perhaps treat those as external content? I’d start by looking at the files in the project tree… that 20Mb has to come from somewhere obvious – large graphics, etc.