title: But I don't want that .lib or .exp file for my COM library!
body: <p>When generating a COM dll with VisualStudio, all I <em>really</em> need is the <code>DllCanUnloadNow</code> symbol (and three related ones) to be exported from the dll itself.  <em>Nobody</em> is going to link against my library, so I'm not (at all) interested in a .lib file, nor in an .exp file.</p>
  
  <p>However, I don't manage to inhibit creation of these files.    (note: I do know how it's possible to remove them in a post-build step)</p>
  
  <p>These are my linker arguments:</p>
  
  <pre><code>/OUT:"u:/cada-nt/bin/PData.dll" 
  /INCREMENTAL:NO 
  /NOLOGO 
  /DLL 
  /MANIFEST:NO 
  /DEF:"PData.def" 
  /DEBUG 
  /PDB:"u:/cada-nt/pdb/PData.pdb" 
  /ERRORREPORT:PROMPT kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib 
                      advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib 
                      odbc32.lib odbccp32.lib
  </code></pre>
  
  <p>The question:</p>
  
  <ul>
  <li>Has anyone succeeded in <em>not</em> generating the .lib and .exp files?</li>
  <li>Does anyone know <em>why</em> these files are generated?</li>
  </ul>