Databases
StackOverflow2013
Postsdbo
POHow to compile a DLL that does not require an external manifest file?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to compile a DLL that does not require an external manifest file?
    text
    copied!<p>I would like to compile a DLL under Visual Studio 2008 that depends on msvcr90.dll as a private assembly (basically I'll dump this DLL into the same directory as my application) without needing an external manifest file.</p> <p>I followed the steps outlined in <a href="http://msdn.microsoft.com/en-us/library/ms235291.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms235291.aspx</a> section <strong>"Deploying Visual C++ library DLLs as private assemblies"</strong> but instead of using an external manifest file (i.e. Microsoft.VC90.CRT.manifest) I'd like to embed it in the DLLs somehow.</p> <p>If I embed Microsoft.VC90.CRT.manifest into msvcr90.dll or the DLL loading it, and remove the external manifest file, LoadLibrary() fails.</p> <p>The problem is when you embed the manifest into a DLL it actually embeds the following:</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?> &lt;assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> &lt;trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> &lt;security> &lt;requestedPrivileges> &lt;requestedExecutionLevel level="asInvoker" uiAccess="false"> &lt;/requestedPrivileges> &lt;/security> &lt;/trustInfo> &lt;dependency> &lt;dependentAssembly> &lt;assemblyIdentity type="win32" name="Microsoft.VC90.DebugCRT" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"> &lt;/dependentAssembly> &lt;/dependency> &lt;/assembly></code></pre> <p>I think the &lt;dependentAssembly> line is what's causing it to die if the manifest file is missing. Any ideas?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload