Whats a manifest file for vc++

Whats the purpose of using the Microsoft.VC90.CRT.manifest file? My program wont run on my testing machine without it..

It contains information about dependencies of your application.

Understood.. Now I read in the Qt deployment article that I need the msvc runtime files and also the manifest file.. Problem is the "version" thats in the manifest for my program is different than the "version" of the manifest where my msvc runtime dlls are kept.. Any idea why this is?

Just to make sure im correct here.. The manifest is to make sure that my program is using the version of the msvc dll's that it was built/tested on correct?

I looked at google earth(written in Qt) and it doesnt have a *.manifest file in the program directory, why is that?

Quote:

---

Originally Posted by tgreaves

Understood.. Now I read in the Qt deployment article that I need the msvc runtime files and also the manifest file.. Problem is the "version" thats in the manifest for my program is different than the "version" of the manifest where my msvc runtime dlls are kept.. Any idea why this is?

---

you might be looking in the wrong place.. look in %windir%/WinSxs: there are several versions of the runtime dlls.

Quote:

---

Just to make sure im correct here.. The manifest is to make sure that my program is using the version of the msvc dll's that it was built/tested on correct?

---

correct. If the versions do not match, you'll get the "Application failed to start ..." error.

Quote:

---

I looked at google earth(written in Qt) and it doesnt have a *.manifest file in the program directory, why is that?

---

the manifest is embedded. If you open the executable with a text/hex editor, scroll to the bottom and you'll find the manifest, example:

Code:

---

<dependency>
    <dependentAssembly>
      <assemblyIdentity type="win32" name="Microsoft.VC90.CRT" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
    </dependentAssembly>
  </dependency>

---

also have a look at dependency walker, a very usefull program to spot dependency problems.

Hi,

Regarding this subject, how can I make qmake read (embedded) manifest file?

I'm asking this because I needed to customize my manifest file(from VS2010) in order to be able to have some writing priviliges on disk(C:).

To do this, I tuned Linker-->Manifest File part accordingly but I'm using qmake built. So I couldn't find how to add my customized Manifest properties into my exe.


In VS2010, the manifest is default embedded. Adding to .pro file;

Code:

---

"CONFIG += embedded_manifest_exe"

---

will be OK?

---

Added after 59 minutes:

What about;

Code:

---

QMAKE_LFLAGS_WINDOWS += /MANIFESTUAC:\"level=\'requireAdministrator\' uiAccess=\'false\'\"

---