Re: [WiX-users] Detecting if IIS is installed

2010-03-01 Thread Nathan . Banek
I did consider this, and I suspect it would work by providing a
different error. The problem is that that error will not be caught as a
part of the conditions, which makes the condition code kind of useless.
In addition, the lengthy delay (3 to 5 minutes) when calculating space
needed that is produced by this missing key would still be present. I
had assumed that the delay would not be there if the check were done by
a condition rather than the cost finalization process. I will try to
change the initial value of the string if that turns out to be the only
way.


-Nathan

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Friday, February 26, 2010 6:43 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Detecting if IIS is installed

If you remove the @Value in Property[Id=IISROOT]?

-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com]
Sent: Wednesday, February 24, 2010 7:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

Didn't mean to imply in my last message that this problem is resolved. I
need a better error to display if IIS is not present on the system. Any
more ideas on how to resolve this? 

Thanks,
-Nathan

-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com]
Sent: Tuesday, February 23, 2010 2:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

The error went away right after I installed IIS on the machine. I
assumed the #0 reference was there because the registry search failed
and the default value of my IISROOT property was '#0'. I would have
thought without IIS on the machine thought that the condition would have
been caught before the registry search failed.

Incidentally, early on I did enable verbose logging, but didn't find a
great deal of help there other than a clue that led me to discover that
IIS was not installed on the machine on which I was testing the
installer (I had assumed it was present).

Thanks,
-Nathan

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, February 23, 2010 12:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

You should get a verbose log and see what's going on. Those network
location messages tend to show up when a property is being used as a
directory and not getting initialized properly. 

Phil Wilson 


-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com]
Sent: Tuesday, February 23, 2010 10:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Detecting if IIS is installed

Greetings,

I have been trying to get my WiX installer to detect whether IIS is
installed on a target system or not (installer is expected to be used on
systems ranging from Windows XP to Windows 7). My problem is that the
detection condition does not seem to be working as my installer hangs on
the opening splashscreen dialog while calculating available space and
then eventually times out with an error saying the Network location #0
could not be reached. It seems that a registry search property I have
defined is being executed before the IIS condition check is performed,
but I'm not sure. Below are the two WiX fragment files with the relevant
code. Does anyone have a suggestion on how I can get my condition check
to occur first so that the installation can be disabled before the cost
calculations are performed?

Thanks,

Nathan Banek

This file is the one with my restrictions and condition checks:

!-- Restrictions.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
Property Id=IIS_MAJOR_VERSION
  RegistrySearch Id=CheckIISVersion Root=HKLM
Key=SOFTWARE\Microsoft\InetStp Name=MajorVersion Type=raw /
/Property

Condition Message=IIS must be installed
  Installed OR IIS_MAJOR_VERSION
/Condition
   
!-- Metabase compatibility is required to allow us to configure the
web site properly --
Property Id=IIS_METABASE_COMPAT
  RegistrySearch Id=CheckIISMetabase Root=HKLM
Key=SOFTWARE\Microsoft\InetStp\Components Name=ADSICompatibility
Type=raw /
/Property

Condition Message=IIS 6 Metabase Compatibility feature must be
installed
  Installed OR ((VersionNT lt; 600) OR IIS_METABASE_COMPAT)
/Condition
  /Fragment
/Wix



In a different wxs file in the project I am attempting to extract the
path to IIS from the registry like so:

!-- WebProduct.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
 
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension
http://schemas.microsoft.com/wix/IIsExtension 
Fragment
Property Id=IISROOT

Re: [WiX-users] Detecting if IIS is installed

2010-02-26 Thread Blair
If you remove the @Value in Property[Id=IISROOT]?

-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com] 
Sent: Wednesday, February 24, 2010 7:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

Didn't mean to imply in my last message that this problem is resolved. I
need a better error to display if IIS is not present on the system. Any
more ideas on how to resolve this? 

Thanks,
-Nathan

-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com] 
Sent: Tuesday, February 23, 2010 2:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

The error went away right after I installed IIS on the machine. I
assumed the #0 reference was there because the registry search failed
and the default value of my IISROOT property was '#0'. I would have
thought without IIS on the machine thought that the condition would have
been caught before the registry search failed.

Incidentally, early on I did enable verbose logging, but didn't find a
great deal of help there other than a clue that led me to discover that
IIS was not installed on the machine on which I was testing the
installer (I had assumed it was present).

Thanks,
-Nathan

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, February 23, 2010 12:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

You should get a verbose log and see what's going on. Those network
location messages tend to show up when a property is being used as a
directory and not getting initialized properly. 

Phil Wilson 


-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com]
Sent: Tuesday, February 23, 2010 10:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Detecting if IIS is installed

Greetings,

I have been trying to get my WiX installer to detect whether IIS is
installed on a target system or not (installer is expected to be used on
systems ranging from Windows XP to Windows 7). My problem is that the
detection condition does not seem to be working as my installer hangs on
the opening splashscreen dialog while calculating available space and
then eventually times out with an error saying the Network location #0
could not be reached. It seems that a registry search property I have
defined is being executed before the IIS condition check is performed,
but I'm not sure. Below are the two WiX fragment files with the relevant
code. Does anyone have a suggestion on how I can get my condition check
to occur first so that the installation can be disabled before the cost
calculations are performed?

Thanks,

Nathan Banek

This file is the one with my restrictions and condition checks:

!-- Restrictions.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
Property Id=IIS_MAJOR_VERSION
  RegistrySearch Id=CheckIISVersion Root=HKLM
Key=SOFTWARE\Microsoft\InetStp Name=MajorVersion Type=raw /
/Property

Condition Message=IIS must be installed
  Installed OR IIS_MAJOR_VERSION
/Condition
   
!-- Metabase compatibility is required to allow us to configure the
web site properly --
Property Id=IIS_METABASE_COMPAT
  RegistrySearch Id=CheckIISMetabase Root=HKLM
Key=SOFTWARE\Microsoft\InetStp\Components Name=ADSICompatibility
Type=raw /
/Property

Condition Message=IIS 6 Metabase Compatibility feature must be
installed
  Installed OR ((VersionNT lt; 600) OR IIS_METABASE_COMPAT)
/Condition
  /Fragment
/Wix



In a different wxs file in the project I am attempting to extract the
path to IIS from the registry like so:

!-- WebProduct.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
 
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension
http://schemas.microsoft.com/wix/IIsExtension 
Fragment
Property Id=IISROOT Value=#0
RegistrySearch Id=IISROOT Type=raw
Root=HKLM Key=Software\Microsoft\InetStp Name=PathWWWRoot /
/Property
DirectoryRef Id=ProgramFilesFolder
Directory Id=IISROOT Name=.
/Directory
/DirectoryRef
/Fragment
/Wix 

 

 


--
Download Intel#174; Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users

Re: [WiX-users] Detecting if IIS is installed

2010-02-24 Thread Nathan . Banek
Didn't mean to imply in my last message that this problem is resolved. I
need a better error to display if IIS is not present on the system. Any
more ideas on how to resolve this? 

Thanks,
-Nathan

-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com] 
Sent: Tuesday, February 23, 2010 2:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

The error went away right after I installed IIS on the machine. I
assumed the #0 reference was there because the registry search failed
and the default value of my IISROOT property was '#0'. I would have
thought without IIS on the machine thought that the condition would have
been caught before the registry search failed.

Incidentally, early on I did enable verbose logging, but didn't find a
great deal of help there other than a clue that led me to discover that
IIS was not installed on the machine on which I was testing the
installer (I had assumed it was present).

Thanks,
-Nathan

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, February 23, 2010 12:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

You should get a verbose log and see what's going on. Those network
location messages tend to show up when a property is being used as a
directory and not getting initialized properly. 

Phil Wilson 


-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com]
Sent: Tuesday, February 23, 2010 10:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Detecting if IIS is installed

Greetings,

I have been trying to get my WiX installer to detect whether IIS is
installed on a target system or not (installer is expected to be used on
systems ranging from Windows XP to Windows 7). My problem is that the
detection condition does not seem to be working as my installer hangs on
the opening splashscreen dialog while calculating available space and
then eventually times out with an error saying the Network location #0
could not be reached. It seems that a registry search property I have
defined is being executed before the IIS condition check is performed,
but I'm not sure. Below are the two WiX fragment files with the relevant
code. Does anyone have a suggestion on how I can get my condition check
to occur first so that the installation can be disabled before the cost
calculations are performed?

Thanks,

Nathan Banek

This file is the one with my restrictions and condition checks:

!-- Restrictions.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
Property Id=IIS_MAJOR_VERSION
  RegistrySearch Id=CheckIISVersion Root=HKLM
Key=SOFTWARE\Microsoft\InetStp Name=MajorVersion Type=raw /
/Property

Condition Message=IIS must be installed
  Installed OR IIS_MAJOR_VERSION
/Condition
   
!-- Metabase compatibility is required to allow us to configure the
web site properly --
Property Id=IIS_METABASE_COMPAT
  RegistrySearch Id=CheckIISMetabase Root=HKLM
Key=SOFTWARE\Microsoft\InetStp\Components Name=ADSICompatibility
Type=raw /
/Property

Condition Message=IIS 6 Metabase Compatibility feature must be
installed
  Installed OR ((VersionNT lt; 600) OR IIS_METABASE_COMPAT)
/Condition
  /Fragment
/Wix



In a different wxs file in the project I am attempting to extract the
path to IIS from the registry like so:

!-- WebProduct.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
 
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension
http://schemas.microsoft.com/wix/IIsExtension 
Fragment
Property Id=IISROOT Value=#0
RegistrySearch Id=IISROOT Type=raw
Root=HKLM Key=Software\Microsoft\InetStp Name=PathWWWRoot /
/Property
DirectoryRef Id=ProgramFilesFolder
Directory Id=IISROOT Name=.
/Directory
/DirectoryRef
/Fragment
/Wix 

 

 


--
Download Intel#174; Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you

Re: [WiX-users] Detecting if IIS is installed

2010-02-23 Thread Wilson, Phil
You should get a verbose log and see what's going on. Those network location 
messages tend to show up when a property is being used as a directory and not 
getting initialized properly. 

Phil Wilson 


-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com] 
Sent: Tuesday, February 23, 2010 10:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Detecting if IIS is installed

Greetings,

I have been trying to get my WiX installer to detect whether IIS is
installed on a target system or not (installer is expected to be used on
systems ranging from Windows XP to Windows 7). My problem is that the
detection condition does not seem to be working as my installer hangs on
the opening splashscreen dialog while calculating available space and
then eventually times out with an error saying the Network location #0
could not be reached. It seems that a registry search property I have
defined is being executed before the IIS condition check is performed,
but I'm not sure. Below are the two WiX fragment files with the relevant
code. Does anyone have a suggestion on how I can get my condition check
to occur first so that the installation can be disabled before the cost
calculations are performed?

Thanks,

Nathan Banek

This file is the one with my restrictions and condition checks:

!-- Restrictions.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
Property Id=IIS_MAJOR_VERSION
  RegistrySearch Id=CheckIISVersion Root=HKLM
Key=SOFTWARE\Microsoft\InetStp Name=MajorVersion Type=raw /
/Property

Condition Message=IIS must be installed
  Installed OR IIS_MAJOR_VERSION
/Condition
   
!-- Metabase compatibility is required to allow us to configure the
web site properly --
Property Id=IIS_METABASE_COMPAT
  RegistrySearch Id=CheckIISMetabase Root=HKLM
Key=SOFTWARE\Microsoft\InetStp\Components Name=ADSICompatibility
Type=raw /
/Property

Condition Message=IIS 6 Metabase Compatibility feature must be
installed
  Installed OR ((VersionNT lt; 600) OR IIS_METABASE_COMPAT)
/Condition
  /Fragment
/Wix



In a different wxs file in the project I am attempting to extract the
path to IIS from the registry like so:

!-- WebProduct.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
 
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension
http://schemas.microsoft.com/wix/IIsExtension 
Fragment
Property Id=IISROOT Value=#0
RegistrySearch Id=IISROOT Type=raw
Root=HKLM Key=Software\Microsoft\InetStp Name=PathWWWRoot /
/Property
DirectoryRef Id=ProgramFilesFolder
Directory Id=IISROOT Name=.
/Directory
/DirectoryRef
/Fragment
/Wix 

 

 

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
affiliates).



--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during 

Re: [WiX-users] Detecting if IIS is installed

2010-02-23 Thread Nathan . Banek
The error went away right after I installed IIS on the machine. I
assumed the #0 reference was there because the registry search failed
and the default value of my IISROOT property was '#0'. I would have
thought without IIS on the machine thought that the condition would have
been caught before the registry search failed.

Incidentally, early on I did enable verbose logging, but didn't find a
great deal of help there other than a clue that led me to discover that
IIS was not installed on the machine on which I was testing the
installer (I had assumed it was present).

Thanks,
-Nathan

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Tuesday, February 23, 2010 12:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if IIS is installed

You should get a verbose log and see what's going on. Those network
location messages tend to show up when a property is being used as a
directory and not getting initialized properly. 

Phil Wilson 


-Original Message-
From: nathan.ba...@l-3com.com [mailto:nathan.ba...@l-3com.com]
Sent: Tuesday, February 23, 2010 10:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Detecting if IIS is installed

Greetings,

I have been trying to get my WiX installer to detect whether IIS is
installed on a target system or not (installer is expected to be used on
systems ranging from Windows XP to Windows 7). My problem is that the
detection condition does not seem to be working as my installer hangs on
the opening splashscreen dialog while calculating available space and
then eventually times out with an error saying the Network location #0
could not be reached. It seems that a registry search property I have
defined is being executed before the IIS condition check is performed,
but I'm not sure. Below are the two WiX fragment files with the relevant
code. Does anyone have a suggestion on how I can get my condition check
to occur first so that the installation can be disabled before the cost
calculations are performed?

Thanks,

Nathan Banek

This file is the one with my restrictions and condition checks:

!-- Restrictions.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
Property Id=IIS_MAJOR_VERSION
  RegistrySearch Id=CheckIISVersion Root=HKLM
Key=SOFTWARE\Microsoft\InetStp Name=MajorVersion Type=raw /
/Property

Condition Message=IIS must be installed
  Installed OR IIS_MAJOR_VERSION
/Condition
   
!-- Metabase compatibility is required to allow us to configure the
web site properly --
Property Id=IIS_METABASE_COMPAT
  RegistrySearch Id=CheckIISMetabase Root=HKLM
Key=SOFTWARE\Microsoft\InetStp\Components Name=ADSICompatibility
Type=raw /
/Property

Condition Message=IIS 6 Metabase Compatibility feature must be
installed
  Installed OR ((VersionNT lt; 600) OR IIS_METABASE_COMPAT)
/Condition
  /Fragment
/Wix



In a different wxs file in the project I am attempting to extract the
path to IIS from the registry like so:

!-- WebProduct.wxs --
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
http://schemas.microsoft.com/wix/2006/wi 
 
xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension
http://schemas.microsoft.com/wix/IIsExtension 
Fragment
Property Id=IISROOT Value=#0
RegistrySearch Id=IISROOT Type=raw
Root=HKLM Key=Software\Microsoft\InetStp Name=PathWWWRoot /
/Property
DirectoryRef Id=ProgramFilesFolder
Directory Id=IISROOT Name=.
/Directory
/DirectoryRef
/Fragment
/Wix 

 

 


--
Download Intel#174; Parallel Studio Eval Try the new software tools for
yourself. Speed compiling, find bugs proactively, and fine-tune
applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you have received it in error, you are on notice
of its status. Please notify the sender immediately by reply e-mail and
then delete this message from your system. Please do not copy it or use
it for any purposes, or disclose its contents to any other person. This
email comes from a division of the Invensys Group, owned by Invensys
plc, which is a company registered in England and Wales with its
registered office at Portland House, Bressenden