Groups | Blog | Home
all groups > visual c > october 2007 >

visual c : Problems with Manifest generation


Havatcha
10/31/2007 3:37:43 PM
I have recently ported a project from VS .Net to VS 2005 and when I
build/run it I get a run-time error "R6034".
After a bit of poking around I discovered that my manifest file only
contains the following

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
</assembly>



When I replace this with the manifest from a functioning program:

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
<dependency>
<dependentAssembly>
<assemblyIdentity type='win32' name='Microsoft.VC80.CRT'
version='8.0.50608.0' processorArchitecture='x86'
publicKeyToken='1fc8b3b9a1e18e3b' />
</dependentAssembly>
</dependency>
</assembly>


The executable runs without a hitch.


Any suggestions on what settings I need to change to generate my
Jochen Kalmbach [MVP]
10/31/2007 7:33:05 PM
Hi Havatcha!

[quoted text, click to view]

Normally the pragma-manifest-statement is automatically embedded, if you
include one of the CRT files!
Just insert an

#include <stdio.h>

and be sure you are using the DLL version of the CRT in your project
setting!
Then the CRT-manifest will be automaticalle generated.


--
Greetings
Jochen

My blog about Win32 and .NET
Havatcha
11/1/2007 3:17:59 PM
[quoted text, click to view]



Thanks for the reply, I checked the Runtime library option in

Configuration Properties -> C/C++ -> Code Generation -> Runtime Library

AddThis Social Bookmark Button