See comment 28.
After I removed the whitespaces in requestedExecutionLevel, I've never looked the error.
Attachment #392442 - Flags: review?(VYV03354) → review+
Comment on attachment 392442 [details] [diff] [review] fix OK, it definitely solved double requestedExecutionLevel problem.
Attachment #392442 - Flags: review?(ted.mielczarek) → review+
Comment on attachment 392442 [details] [diff] [review] fix I don't understand why this would fix it, but it looks harmless, and I'll take your and Masatoshi's word for it.
Pushed to mozilla-central: http://hg.mozilla.org/mozilla-central/rev/285a17333d0b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
For reference, let me explain what happens here. MSVC9 linker tries to find requestedExecutionLevel from an existing manifest. If it is not found, the linker will add it. The linker fails to find an existing requestedExecutionLevel if it contains white spaces. So it will add another requestedExecutionLevel because the linker thinks it is not present yet. Vista/7 consider the manifest is broken and ignore it if it contains duplicate requestedExecutionLevel. We have two options to deal with the problem: 1. Add /MANIFESTUAC:NO linker flag as bug 419665 did. 2. Remove extra white spaces from requestedExecutionLevel as this bug did.
Thanks for the explanation. This seems like the simplest fix, then.
You need to log in before you can comment on or make changes to this bug.