Re: [WiX-users] Vista registry virtualization

2008-03-06 Thread Simon Topley
Thanks again Bob, using the right WiX elements seems to have done the
trick. All this registry hardcoded lark was added while I was on
holiday, I take no responsibility!

Simon 

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 05 March 2008 05:12
To: Simon Topley
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Vista registry virtualization

Simon Topley wrote:
> I suspect that I am registering the interfaces incorrectly. I'm adding

> all of the details manually (CLSID, TYPELIB blah blah blah) maybe 
> there is a COM registration component I'm not aware of that would take

> care of this.

Are you using Registry/RegistryKey/RegistryValue? Which registry roots? 
The WiX elements Class/ProgId/Interface/etc write the correct registry
values for both per-machine and per-user installs.

--
sig://boB
http://joyofsetup.com/


The information contained in this e-mail is likely to be confidential and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately at
the above address. The disclosure, copying or distribution of this message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in reliance
upon them.

Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Vista registry virtualization

2008-03-05 Thread Roy Abou Assaly


Simon Topley wrote:
> 
> We have recently been having issues with our COM interface and the
> finger was pointed at the installers as ever. It seems in vista being
> logged in as an Administrator doesn't mean what it once did. Most
> programs are run by default as a user, you have to right click and "run
> as administrator" then sign you name in blood and answer a phone in
> central park within 5 minutes. When our software is run by a user it
> uses some other virtual store hive that obviously doesn't contain the
> COM registration for our product. All is well if you run as
> administrator.
> 
> ...
> 
> I suspect that I am registering the interfaces incorrectly. I'm adding
> all of the details manually (CLSID, TYPELIB blah blah blah) maybe there
> is a COM registration component I'm not aware of that would take care of
> this. If not then I'm not sure where the fix should be, should I be
> adding this data to the registry with different permission levels or is
> the problem in the software in the way we read from the registry (with a
> KEY_READ which gets no redirection or KEY_ALL_ACCESS which gets the
> redirection and make KEY_READ kind of pointless)
> 

Hi,

Even though you are local admin on your machine, the process must be
"elevated".  
For MSI, you get prompted for the elevation (correct me if I'm wrong). 
However,
If you run any other process that attempts to register those DLLs without
elevation,
then the keys get registered in the virtual store.  I highly recommend you
delete any
entries in your virtual store that are related to your current installation
because the 
virtualstore takes precedence over the real entries.  For example,

You register x.dll without enough privilege
It gets registered to your virtualstore
x.dll gets updated
You register x.dll *with* privilege
It get registered to your HKLM.
When your app runs, it will reference your virtualstore and never touch
HKLM.
solution:  delete the entry in your virtualstore and your HKLM will be
referenced.

That's what I found from my experience.  So be aware that if anything gets
installed without enough privilege, you have to go and clean up that mess.

I've struggled without migration to Vista, and so that was one of the
lessons I learned.

Good luck.

Roy
-- 
View this message in context: 
http://www.nabble.com/Vista-registry-virtualization-tp15824051p15854551.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Vista registry virtualization

2008-03-05 Thread Simon Topley
Hi Bob!

Yes I am using Registry/Key/Value in HKLM. I'll have a play with these
Class/ProgId/interface puppies later today sounds like just the ticket,
thanks for the help again.

Simon

-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED] 
Sent: 05 March 2008 05:12
To: Simon Topley
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Vista registry virtualization

Simon Topley wrote:
> I suspect that I am registering the interfaces incorrectly. I'm adding

> all of the details manually (CLSID, TYPELIB blah blah blah) maybe 
> there is a COM registration component I'm not aware of that would take

> care of this.

Are you using Registry/RegistryKey/RegistryValue? Which registry roots? 
The WiX elements Class/ProgId/Interface/etc write the correct registry
values for both per-machine and per-user installs.

--
sig://boB
http://joyofsetup.com/


The information contained in this e-mail is likely to be confidential and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately at
the above address. The disclosure, copying or distribution of this message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in reliance
upon them.

Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Vista registry virtualization

2008-03-04 Thread Bob Arnson
Simon Topley wrote:
> I suspect that I am registering the interfaces incorrectly. I'm adding
> all of the details manually (CLSID, TYPELIB blah blah blah) maybe there
> is a COM registration component I'm not aware of that would take care of
> this. 

Are you using Registry/RegistryKey/RegistryValue? Which registry roots? 
The WiX elements Class/ProgId/Interface/etc write the correct registry 
values for both per-machine and per-user installs.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Vista registry virtualization

2008-03-04 Thread Simon Topley
Hello all,

We have recently been having issues with our COM interface and the
finger was pointed at the installers as ever. It seems in vista being
logged in as an Administrator doesn't mean what it once did. Most
programs are run by default as a user, you have to right click and "run
as administrator" then sign you name in blood and answer a phone in
central park within 5 minutes. When our software is run by a user it
uses some other virtual store hive that obviously doesn't contain the
COM registration for our product. All is well if you run as
administrator.

More details about this registry lark here:

http://msdn2.microsoft.com/fr-fr/library/aa965884.aspx

I suspect that I am registering the interfaces incorrectly. I'm adding
all of the details manually (CLSID, TYPELIB blah blah blah) maybe there
is a COM registration component I'm not aware of that would take care of
this. If not then I'm not sure where the fix should be, should I be
adding this data to the registry with different permission levels or is
the problem in the software in the way we read from the registry (with a
KEY_READ which gets no redirection or KEY_ALL_ACCESS which gets the
redirection and make KEY_READ kind of pointless)

I look forward to your response (Mike or Bob ;) )

Simon

The information contained in this e-mail is likely to be confidential and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately at
the above address. The disclosure, copying or distribution of this message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in reliance
upon them.

Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users