I had a similar issue with my build a while back
and I ended up finding out that something in our build chain was corrupting
the manifest (the manifest had two different xml namespaces referring to two
different versions of the manifest versions if I recall correctly).The
solution for me was to change the manifest file
(src\chrome\app\chrome.exe.manifest) to contain only the XML header only.
Then the toolchain updated it correctly.
This is from memory so I hope this helps (I no longer have this problem).
Sverrir
On Tue, Jun 2, 2009 at 12:44 PM, nakro <yoav.zilberb...@gmail.com> wrote:
>
> Raul, right now i am in the middle of (yet another) clobber build so i
> can't test this
> all i want to know is this
> imagine you have UAC enabled, and you just press F11 on setup.exe in
> VS
> does it really launch on your machine without this error ?
>
> i am not looking for a way to solve it (i am aware of tricks to
> bypass)
> all i am trying to figure is what is so different about my environment
>
> a simple Y for yes i can would convince me that somehow i messed my
> env
> which would at least be something
>
> thanx a lot
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
