msvs generator doesn't consider the AdditionalManifestFiles property

[GoogleCodeExporter]

Here is an example of this property being used: 
http://code.google.com/searchframe#OAMlx_jo-ck/src/chrome/chrome_installer.gypi&
exact_package=chromium&q=setup.exe.manifest&type=cs&l=269

In VS2008 this correctly puts the extra manifest properties in the embedded 
manifest in the target, setup.exe.

In VS2010 builds the default manifest is embedded and the 
"AdditionalManifestFiles" are ignored.

Original issue reported on code.google.com by gab@chromium.org on 11 May 2012 at 1:26

• Merged into: #222

[GoogleCodeExporter]

Original comment by grt@chromium.org on 11 May 2012 at 1:27

• Changed state: Accepted

[GoogleCodeExporter]

Since we only have one manifest per executable, it'd be better in many respects 
to embed them manually from a resource file than to use the manifest tool.

Original comment by siggi@chromium.org on 11 May 2012 at 1:33

[GoogleCodeExporter]

I believe this is a dupe of bug 222.

Original comment by robertsh...@chromium.org on 11 May 2012 at 1:49

• Changed state: Duplicate