[WiX-users] RegistrySearch fails, returns C: or Empty

2011-10-25 Thread Leo Koivuniemi
Hello all,

I am having some problems with an installation using Wix v3
During install of application I run

Property Id=SETUPFOLDER
RegistrySearch Id=SETUPFOLDER Root=HKCU
Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder
Type=raw /
/Property

SETUPFOLDER is later used for setting the target of a shortcut in the start
menu. This works when I install or reinstall by running my bootstrapper
setup.exe which then starts the MSI package. But when applying patches for
instance or bypassig the setup.exe and running the MSI directly, then the
registry search returns C: or is just empty. When I check that path in
registry using regedit then I do find the correct value there but for some
reason the RegistrySearch fails and I can't figure out why.

Notable is that this error does not exist in Windows XP, but now as I have
been porting it to Windows 7 I noticed this problem. So basically the code
should work, but it doesn't do that in Win7 (only works if I go through the
bootstrapper exe)

Any suggestions?

Thanks!

Leo
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RegistrySearch fails, returns C: or Empty

2011-10-25 Thread Rob Mensching
What does the verbose log file show?

On Tue, Oct 25, 2011 at 8:10 AM, Leo Koivuniemi 
universalserial...@gmail.com wrote:

 Hello all,

 I am having some problems with an installation using Wix v3
 During install of application I run

 Property Id=SETUPFOLDER
 RegistrySearch Id=SETUPFOLDER Root=HKCU
 Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder
 Type=raw /
 /Property

 SETUPFOLDER is later used for setting the target of a shortcut in the start
 menu. This works when I install or reinstall by running my bootstrapper
 setup.exe which then starts the MSI package. But when applying patches for
 instance or bypassig the setup.exe and running the MSI directly, then the
 registry search returns C: or is just empty. When I check that path in
 registry using regedit then I do find the correct value there but for some
 reason the RegistrySearch fails and I can't figure out why.

 Notable is that this error does not exist in Windows XP, but now as I have
 been porting it to Windows 7 I noticed this problem. So basically the code
 should work, but it doesn't do that in Win7 (only works if I go through the
 bootstrapper exe)

 Any suggestions?

 Thanks!

 Leo

 --
 The demand for IT networking professionals continues to grow, and the
 demand for specialized networking skills is growing even more rapidly.
 Take a complimentary Learning@Cisco Self-Assessment and learn
 about Cisco certifications, training, and career opportunities.
 http://p.sf.net/sfu/cisco-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RegistrySearch fails, returns C: or Empty

2011-10-25 Thread Leo Koivuniemi
Hi,
thanks for fast reply!

In the MSI log I can see that it actually finds the correct SETUPFOLDER path
from registry, but then there are some rows saying:
Ignoring disallowed property SETUPFOLDER

But I can see that it finds the correct path because further down in the log
I have something like

AppSearch: Property: SETUPFOLDER, Signature: SETUPFOLDER
MSI (c) (F0:80) [17:32:47:087]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (F0:80) [17:32:47:087]: PROPERTY CHANGE: Adding SETUPFOLDER
property. Its value is '\\rrdb\xxx\xxx\Setup'.

And then an .ini file is written and it now the log (almost at the very end)
says:

MSI (s) (3C:44) [17:34:07:697]: Executing op:
IniWriteRemoveValue(Section=INSTANCE,Key=SetupFolder,,Mode=0)
WriteIniValues: File: xxx.ini,  Section: INSTANCE,  Key: SetupFolder,
Value:

Note that the value: is empty.

And then at the very very end of the log file it states the properties:

Property(C): SETUPFOLDER = \\rrdb\xxx\xxx\Setup

So again it has the correct value but it does not want to use it when
specifying the target of the shortcut.

Hope this gives you some idea...

Thankful for help!

2011/10/25 Rob Mensching r...@robmensching.com

 What does the verbose log file show?

 On Tue, Oct 25, 2011 at 8:10 AM, Leo Koivuniemi 
 universalserial...@gmail.com wrote:

  Hello all,
 
  I am having some problems with an installation using Wix v3
  During install of application I run
 
  Property Id=SETUPFOLDER
  RegistrySearch Id=SETUPFOLDER Root=HKCU
  Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder
  Type=raw /
  /Property
 
  SETUPFOLDER is later used for setting the target of a shortcut in the
 start
  menu. This works when I install or reinstall by running my bootstrapper
  setup.exe which then starts the MSI package. But when applying patches
 for
  instance or bypassig the setup.exe and running the MSI directly, then the
  registry search returns C: or is just empty. When I check that path in
  registry using regedit then I do find the correct value there but for
 some
  reason the RegistrySearch fails and I can't figure out why.
 
  Notable is that this error does not exist in Windows XP, but now as I
 have
  been porting it to Windows 7 I noticed this problem. So basically the
 code
  should work, but it doesn't do that in Win7 (only works if I go through
 the
  bootstrapper exe)
 
  Any suggestions?
 
  Thanks!
 
  Leo
 
 
 --
  The demand for IT networking professionals continues to grow, and the
  demand for specialized networking skills is growing even more rapidly.
  Take a complimentary Learning@Cisco Self-Assessment and learn
  about Cisco certifications, training, and career opportunities.
  http://p.sf.net/sfu/cisco-dev2dev
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 


 --
 virtually, Rob Mensching - http://RobMensching.com LLC

 --
 The demand for IT networking professionals continues to grow, and the
 demand for specialized networking skills is growing even more rapidly.
 Take a complimentary Learning@Cisco Self-Assessment and learn
 about Cisco certifications, training, and career opportunities.
 http://p.sf.net/sfu/cisco-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RegistrySearch fails, returns C: or Empty

2011-10-25 Thread Leo Koivuniemi
Hi again,

I believe I solved it (haven't done enough testing yet though!)!
It seems that the property had to be set as Secure=yes since otherwise UAC
will not allow it.

Will get back to you if I find that it is not solved. But I just tried an
installation that earlier did not work and now it did!

Thanks for all help so far anyway!
Leo

2011/10/25 Leo Koivuniemi universalserial...@gmail.com

 Hi,
 thanks for fast reply!

 In the MSI log I can see that it actually finds the correct SETUPFOLDER
 path from registry, but then there are some rows saying:
 Ignoring disallowed property SETUPFOLDER

 But I can see that it finds the correct path because further down in the
 log I have something like

 AppSearch: Property: SETUPFOLDER, Signature: SETUPFOLDER
 MSI (c) (F0:80) [17:32:47:087]: Note: 1: 2262 2: Signature 3: -2147287038
 MSI (c) (F0:80) [17:32:47:087]: PROPERTY CHANGE: Adding SETUPFOLDER
 property. Its value is '\\rrdb\xxx\xxx\Setup'.

 And then an .ini file is written and it now the log (almost at the very
 end) says:

 MSI (s) (3C:44) [17:34:07:697]: Executing op:
 IniWriteRemoveValue(Section=INSTANCE,Key=SetupFolder,,Mode=0)
 WriteIniValues: File: xxx.ini,  Section: INSTANCE,  Key: SetupFolder,
 Value:

 Note that the value: is empty.

 And then at the very very end of the log file it states the properties:

 Property(C): SETUPFOLDER = \\rrdb\xxx\xxx\Setup

 So again it has the correct value but it does not want to use it when
 specifying the target of the shortcut.

 Hope this gives you some idea...

 Thankful for help!

 2011/10/25 Rob Mensching r...@robmensching.com

 What does the verbose log file show?

 On Tue, Oct 25, 2011 at 8:10 AM, Leo Koivuniemi 
 universalserial...@gmail.com wrote:

  Hello all,
 
  I am having some problems with an installation using Wix v3
  During install of application I run
 
  Property Id=SETUPFOLDER
  RegistrySearch Id=SETUPFOLDER Root=HKCU
  Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder
  Type=raw /
  /Property
 
  SETUPFOLDER is later used for setting the target of a shortcut in the
 start
  menu. This works when I install or reinstall by running my bootstrapper
  setup.exe which then starts the MSI package. But when applying patches
 for
  instance or bypassig the setup.exe and running the MSI directly, then
 the
  registry search returns C: or is just empty. When I check that path in
  registry using regedit then I do find the correct value there but for
 some
  reason the RegistrySearch fails and I can't figure out why.
 
  Notable is that this error does not exist in Windows XP, but now as I
 have
  been porting it to Windows 7 I noticed this problem. So basically the
 code
  should work, but it doesn't do that in Win7 (only works if I go through
 the
  bootstrapper exe)
 
  Any suggestions?
 
  Thanks!
 
  Leo
 
 
 --
  The demand for IT networking professionals continues to grow, and the
  demand for specialized networking skills is growing even more rapidly.
  Take a complimentary Learning@Cisco Self-Assessment and learn
  about Cisco certifications, training, and career opportunities.
  http://p.sf.net/sfu/cisco-dev2dev
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 


 --
 virtually, Rob Mensching - http://RobMensching.com LLC

 --
 The demand for IT networking professionals continues to grow, and the
 demand for specialized networking skills is growing even more rapidly.
 Take a complimentary Learning@Cisco Self-Assessment and learn
 about Cisco certifications, training, and career opportunities.
 http://p.sf.net/sfu/cisco-dev2dev
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users