Sverir, thank you very much for your reply, i posted this as a
possible bug
plus ideas on how to fix this
http://code.google.com/p/chromium/issues/detail?id=13239
i am still not sure why it only happens on my machine, as i am sure
all of you have no issues
but i am no manifest expert in any
No problem. Are you using Visual Studio 2008? Since the official builders
are on VS2005 I suspect there are some incompatibilities between the
toolchains on those two.
Sverrir
On Wed, Jun 3, 2009 at 8:06 AM, nakro yoav.zilberb...@gmail.com wrote:
Sverir, thank you very much for your reply,
On Tue, Jun 2, 2009 at 3:11 AM, nakro yoav.zilberb...@gmail.com wrote:
and to make the UI tests pass, chromium has to be the default browser
(especially on hebrew vista)
Not anymore, see http://code.google.com/p/chromium/issues/detail?id=13064
M-A
Not sure why you are getting error when setup.exe gets launched but to get
around it you can launch Chrome as admin, set it as default and then exit.
On Tue, Jun 2, 2009 at 12:11 AM, nakro yoav.zilberb...@gmail.com wrote:
setting chromium as the default browser make it invoke setup.exe
the
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
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
