I think I have found it, I'm not sure of a nice way to work around it
though. I've copied some code that launches IE after an install (this is
an IE only install, so no problem there) but it runs in the context of
the UI. I'm led to believe that this is where I'm mucking things up. You
can see
You could be right. The DLL could be doing something daft. I thought I
tallowed out all the registration. I'll check again.
Rob Hamflett wrote:
> If you're doing things via normal MSI methods (which you are, assuming the
> values are correct) and
> specifying [EMAIL PROTECTED]"elevated" (are yo
If you're doing things via normal MSI methods (which you are, assuming the
values are correct) and
specifying [EMAIL PROTECTED]"elevated" (are you?), then I'm out of ideas, sorry.
Aha, hold on. When you run from the elevated command prompt, the entire
installation runs elevated.
This means
The registration of the DLL is handled via RegistryValue elements
wrapped inside Component elements which are then inside three levels of
Directory elements (snippet below). So no custom actions involved for
the registry, I kind of got the impression they were not good. I do have
one however, t
That article is missing a few important bits, as far as my understanding goes.
An installer written
for Vista should be marked as needing elevation, or not needing elevation. If
it does, you get
prompted when the installer switches over to the server side, which does the
actual work. Micros
Been looking into this some more. I've asked the customer to log before
and after (nothing yet) but in the meantime they found this article on
how to elevate privileges for an MSI (
http://footheory.com/blogs/shane/archive/2007/08/03/vista-and-elevating-security-of-an-msi-to-run-as-administrator
The only thing that I can think to cause this would be if the command prompt
was elevated. Have you
tried logging the installation to see what the differences are? This article
explains how to turn
on global logging so you can get the logs for the double-click installation.
http://support.mi
Ah, sorry, didn't see you there amongst all the spam!
I mean that from a command prompt it installs the Browser Helper Object
DLL just fine, but when run via double clicking it does not. It appears
to work the same but the DLL is not registered properly and does not get
installed into IE. But, thi
You say it runs fine from a command prompt. How does it normally run?
Rob
Ryan O'Neill wrote:
> Anyone got a clue about this? I can't resolve it.
>
> Ryan O'Neill wrote:
>> Hi all,
>>
>> I have an installer that works great for all Win platforms, except Vista
>> where it will fail to register
Anyone got a clue about this? I can't resolve it.
Ryan O'Neill wrote:
> Hi all,
>
> I have an installer that works great for all Win platforms, except Vista
> where it will fail to register a DLL on specific machines. It runs on
> most Vista installations fine (under admin and limited user accou
Hi all,
I have an installer that works great for all Win platforms, except Vista
where it will fail to register a DLL on specific machines. It runs on
most Vista installations fine (under admin and limited user accounts
which prompt for admin access). I did manage to get to a machine that
exhi
11 matches
Mail list logo
