Help - Missing manifest file

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RD - 19 Sep 2007 23:24 GMT

I'm working on migrating my VC++ 6.0 project to VS C++ 2005 and I'm bulding
the project using NMAKE from the command line. The code is not GUI, all
console utilities and services. I've managed to compile/build the code but
couple of places in my build tree I don't see manifest file along with DLL
and/or EXE. In most dirs. it (*.manifest) is there except for few and I
wonder what could be the reason for that. I'm not using /manifest switch any
where in my Makefiles. If I tries to open the exe file, that doesn't have
manifest file, in VS2005 Prof Ed. IDE, I get error "Cannot enumerate
resources in the executable.". Any help?

Reply to this Message

RD - 21 Sep 2007 23:04 GMT

DLL/EXEs, where the *.manifest file were missing, were compiled with /MT
switch (static link). I changed it to /MD (dynamic link) and it created the
manifest file. I guess if you are linking statically you don't have any
runtime dependency and thus no manifest file.

RD

> I'm working on migrating my VC++ 6.0 project to VS C++ 2005 and I'm bulding
> the project using NMAKE from the command line. The code is not GUI, all
[quoted text clipped - 5 lines]
> manifest file, in VS2005 Prof Ed. IDE, I get error "Cannot enumerate
> resources in the executable.". Any help?

Reply to this Message

David Wilkinson - 22 Sep 2007 10:47 GMT

> DLL/EXEs, where the *.manifest file were missing, were compiled with /MT
> switch (static link). I changed it to /MD (dynamic link) and it created the
> manifest file. I guess if you are linking statically you don't have any
> runtime dependency and thus no manifest file.

RD:

Even with static linking you still need a manifest to get XP/Vista
themes, and to turn of vitualization and other legacy features in Vista.

Signature

David Wilkinson
Visual C++ MVP

Reply to this Message

RD - 04 Oct 2007 17:44 GMT

I'm writting applications for XP servers only. In that case I won't need
manifest file. Is that correct?

I'm now trying to build an existing DLL without manifestation using
/ALLOWISOLATION:NO and it gives me link error as follows:
LINK : fatal error LNK1295: '/ALLOWISOLATION' not compatible with '/DLL'
specification; link without '/ALLOWISOLATION'

Does this means you can't use link option /ALLOWISOLATION for a DLL. It is
only for the EXEs? I need to build DLL without .manifest file to resolve java
JNI DLL load error with java.exe. Any ideas.

> > DLL/EXEs, where the *.manifest file were missing, were compiled with /MT
> > switch (static link). I changed it to /MD (dynamic link) and it created the
[quoted text clipped - 5 lines]
> Even with static linking you still need a manifest to get XP/Vista
> themes, and to turn of vitualization and other legacy features in Vista.

Reply to this Message

Ben Voigt [C++ MVP] - 09 Oct 2007 15:42 GMT

> I'm writting applications for XP servers only. In that case I won't need
> manifest file. Is that correct?
[quoted text clipped - 8 lines]
> java
> JNI DLL load error with java.exe. Any ideas.

You need to provide "java.exe.manifest"

Reply to this Message

Help - Missing manifest file

Free Magazines