Re: [WiX-users] Fwd: Re: Referring to fragments
arguments, give you some generated
code you can just plug into your project and go. Probably. In
theory. If the planets are all in the correct alignments and
you've made the right sacrifices. In practice, you should
consider whether this kind of dynamic code generation is really
what you need.
Do the contents of that directory change without warning or
beyond your team's ability to keep up with the changes? If so,
then this kind of code generation is potentially a way around the
issue, but ideally you should reconsider the application design.
However, if this is more about generating code so you don't have
to crank it by hand, then I'd recommend taking the generated code
and adding the missing or incorrect attributes (possibly with
PowerShell) and then take that code as source. Further updates to
this code can be done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda
suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject:Fwd: Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 15:06:38 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in
To: John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com
Attaching the source files once again.
Original Message
Subject:Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 15:04:31 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in
To: John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com
CC: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
mailto:wix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program
Files (x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) :
error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in
section 'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name
to TORTDEMO instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string'
Value='' KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(751)
: error LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(754)
: error LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v3.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(757)
: error LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v4.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(760)
: error LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v5.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(763)
: error LGHT0103 :
The system cannot find the file 'SourceDir\tortosedata.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(766)
: error LGHT0103 :
Please suggest on the same.
On 18-11-2013 14:24, John Ludlow wrote:
Ah, I missed that.
You need to create a reference in your feature to each
component, because now you have components which aren't
assigned to any feature, which means they would never be
installed.
Please try this:
1. On your Heat.exe call, specify the -cg argument with a
component name:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg
-sfrag -dr TORTDEMO -out trunkdb.wxs.
This should add a component group with all the components in
the output. The ID should be trunkdb, which you can
reference in your Feature.
2. Change your Feature element like so:
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
ComponentGroupRef Id='trunkdb'/
/Feature
This should reference the component group created in Step
#1, drawing all
Re: [WiX-users] Fwd: Re: Referring to fragments
directory . It is showing for about 150 files in the db directory.
There are a total of 379 files in the same.
Regards,
SuvraJyoti
On 18-11-2013 19:00, John Ludlow wrote:
Do those files exist at compilation time? They are C:\Program Files
(x86) paths, and your code doesn't specify a full path in File/@Source.
I'm not sure how it came up with that path, but it's probably wrong, since
you are likely building your application binaries in a build area.
You will need to either specify the -var argument to heat.exe with a
variable name (and tweak the value so that it matches correctly) or write
some build code to tweak the contents of this file.
Heat.exe can, with the correct arguments, give you some generated code
you can just plug into your project and go. Probably. In theory. If the
planets are all in the correct alignments and you've made the right
sacrifices. In practice, you should consider whether this kind of dynamic
code generation is really what you need.
Do the contents of that directory change without warning or beyond
your team's ability to keep up with the changes? If so, then this kind of
code generation is potentially a way around the issue, but ideally you
should reconsider the application design.
However, if this is more about generating code so you don't have to
crank it by hand, then I'd recommend taking the generated code and adding
the missing or incorrect attributes (possibly with PowerShell) and then
take that code as source. Further updates to this code can be done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda
suvrajyo...@contata.co.inwrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18
Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda
suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com
Attaching the source files once again.
Original Message Subject: Re: [WiX-users] Referring
to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From: Suvrajyoti
Panda suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com CC: General
discussion about the WiX toolset.
wix-users@lists.sourceforge.netwix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program Files
(x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in section
'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to
TORTDEMO instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string' Value=''
KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(751) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(754) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v3.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(757) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v4.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(760) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v5.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(763) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortosedata.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(766) : error
LGHT0103 :
Please suggest on the same.
On 18-11-2013 14:24, John Ludlow wrote:
Ah, I missed that.
You need to create a reference in your feature to each component,
because now you have components which aren't assigned to any feature, which
means they would never be installed.
Please try this:
1. On your Heat.exe call, specify the -cg argument with a component
name:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag -dr
TORTDEMO -out trunkdb.wxs.
This should add a component group with all the components in the
output. The ID should be trunkdb, which you can reference in your Feature.
2. Change your Feature element like so:
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
ComponentGroupRef Id='trunkdb'/
/Feature
This should reference the component group created in Step #1, drawing
all those
Re: [WiX-users] Fwd: Re: Referring to fragments
specify a full path in File/@Source.
I'm not sure how it came up with that path, but it's probably wrong, since
you are likely building your application binaries in a build area.
You will need to either specify the -var argument to heat.exe with a
variable name (and tweak the value so that it matches correctly) or write
some build code to tweak the contents of this file.
Heat.exe can, with the correct arguments, give you some generated code
you can just plug into your project and go. Probably. In theory. If the
planets are all in the correct alignments and you've made the right
sacrifices. In practice, you should consider whether this kind of dynamic
code generation is really what you need.
Do the contents of that directory change without warning or beyond your
team's ability to keep up with the changes? If so, then this kind of code
generation is potentially a way around the issue, but ideally you should
reconsider the application design.
However, if this is more about generating code so you don't have to
crank it by hand, then I'd recommend taking the generated code and adding
the missing or incorrect attributes (possibly with PowerShell) and then
take that code as source. Further updates to this code can be done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda suvrajyo...@contata.co.inwrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18
Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda
suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com
Attaching the source files once again.
Original Message Subject: Re: [WiX-users] Referring
to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From: Suvrajyoti
Panda suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com CC: General
discussion about the WiX toolset.
wix-users@lists.sourceforge.netwix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program Files
(x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in section
'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to TORTDEMO
instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string' Value=''
KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(751) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(754) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v3.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(757) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v4.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(760) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v5.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(763) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortosedata.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(766) : error
LGHT0103 :
Please suggest on the same.
On 18-11-2013 14:24, John Ludlow wrote:
Ah, I missed that.
You need to create a reference in your feature to each component,
because now you have components which aren't assigned to any feature, which
means they would never be installed.
Please try this:
1. On your Heat.exe call, specify the -cg argument with a component
name:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag -dr
TORTDEMO -out trunkdb.wxs.
This should add a component group with all the components in the
output. The ID should be trunkdb, which you can reference in your Feature.
2. Change your Feature element like so:
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
ComponentGroupRef Id='trunkdb'/
/Feature
This should reference the component group created in Step #1, drawing
all those components into that feature.
At first glance, the registry entry you've created looks fine. I'd
probably specify a value, but that's just me.
On 18 November 2013 08:32, Suvrajyoti Panda
suvrajyo...@contata.co.inwrote:
Hi John,
Please also have a look at the directory structure
Re: [WiX-users] Fwd: Re: Referring to fragments
of heat.exe might be able to help you further. Hope that helps On 18 November 2013 14:36, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Hi John, When I are created the trunkdb.wxs file i had ditected it to D:\Project\ESI\Code\trunk\db. These files exist now also and are part of the SVN source control. I do not get what you mean by C:\Program Files (x86) and I'm not sure how it came up with that path . I am just executing Light from the path C:\Program Files (x86)\WiX Toolset v3.7\bin where in my two source files are also placed(tortenginedemo.wxs and trunkdb.wxs). By File/@Source i guess you mean that as of now in the fragment the path is only SourceDIr. Let me know how we can do that. I need this to be dynamic in the sense that a batch file would execute that would create the directory *db**(*D:\Project\ESI\Code\trunk\db*). * The WIX installer that needs to be created should install the “db” directories that is created by the batch file. Basically i need to execute the installer when the scroipts for cruise control are fired. The firing of the cruisecontrol script fires the installer as well through a batch file. This is the approach that has been decided as of now. In case you other pointers do let me know specially the You will need to either specify the -var argument to heat.exe with a variable name (and tweak the value so that it matches correctly) or write some build code to tweak the contents of this file. if this helps. Moreover it is not that the error is being shown foll all the files in the db directory . It is showing for about 150 files in the db directory. There are a total of 379 files in the same. Regards, SuvraJyoti On 18-11-2013 19:00, John Ludlow wrote: Do those files exist at compilation time? They are C:\Program Files (x86) paths, and your code doesn't specify a full path in File/@Source. I'm not sure how it came up with that path, but it's probably wrong, since you are likely building your application binaries in a build area. You will need to either specify the -var argument to heat.exe with a variable name (and tweak the value so that it matches correctly) or write some build code to tweak the contents of this file. Heat.exe can, with the correct arguments, give you some generated code you can just plug into your project and go. Probably. In theory. If the planets are all in the correct alignments and you've made the right sacrifices. In practice, you should consider whether this kind of dynamic code generation is really what you need. Do the contents of that directory change without warning or beyond your team's ability to keep up with the changes? If so, then this kind of code generation is potentially a way around the issue, but ideally you should reconsider the application design. However, if this is more about generating code so you don't have to crank it by hand, then I'd recommend taking the generated code and adding the missing or incorrect attributes (possibly with PowerShell) and then take that code as source. Further updates to this code can be done by hand. Hope that helps On 18 November 2013 11:18, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Hi John, Any updates on the below issue. I am still stuck there. Regards, Suvra Jyoti Original Message Subject:Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in To: John Ludlow john.ludlow...@gmail.com mailto:john.ludlow...@gmail.com Attaching the source files once again. Original Message Subject:Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From: Suvrajyoti Panda suvrajyo
Re: [WiX-users] Fwd: Re: Referring to fragments
Panda
suvrajyo...@contata.co.inwrote:
Hi John,
When I are created the trunkdb.wxs file i had ditected it to
D:\Project\ESI\Code\trunk\db. These files exist now also and are part of
the SVN source control. I do not get what you mean by C:\Program Files
(x86) and I'm not sure how it came up with that path . I am just
executing Light from the path C:\Program Files (x86)\WiX Toolset v3.7\bin
where in my two source files are also placed(tortenginedemo.wxs and
trunkdb.wxs). By File/@Source i guess you mean that as of now in the
fragment the path is only SourceDIr. Let me know how we can do that.
I need this to be dynamic in the sense that a batch file would execute
that would create the directory *db** (*D:\Project\ESI\Code\trunk\db
*). * The WIX installer that needs to be created should install the
“db” directories that is created by the batch file. Basically i need to
execute the installer when the scroipts for cruise control are fired. The
firing of the cruisecontrol script fires the installer as well through a
batch file.
This is the approach that has been decided as of now. In case you other
pointers do let me know specially the You will need to either specify the
-var argument to heat.exe with a variable name (and tweak the value so that
it matches correctly) or write some build code to tweak the contents of
this file. if this helps.
Moreover it is not that the error is being shown foll all the files in
the db directory . It is showing for about 150 files in the db directory.
There are a total of 379 files in the same.
Regards,
SuvraJyoti
On 18-11-2013 19:00, John Ludlow wrote:
Do those files exist at compilation time? They are C:\Program Files
(x86) paths, and your code doesn't specify a full path in File/@Source.
I'm not sure how it came up with that path, but it's probably wrong, since
you are likely building your application binaries in a build area.
You will need to either specify the -var argument to heat.exe with a
variable name (and tweak the value so that it matches correctly) or write
some build code to tweak the contents of this file.
Heat.exe can, with the correct arguments, give you some generated code
you can just plug into your project and go. Probably. In theory. If the
planets are all in the correct alignments and you've made the right
sacrifices. In practice, you should consider whether this kind of dynamic
code generation is really what you need.
Do the contents of that directory change without warning or beyond
your team's ability to keep up with the changes? If so, then this kind of
code generation is potentially a way around the issue, but ideally you
should reconsider the application design.
However, if this is more about generating code so you don't have to
crank it by hand, then I'd recommend taking the generated code and adding
the missing or incorrect attributes (possibly with PowerShell) and then
take that code as source. Further updates to this code can be done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda
suvrajyo...@contata.co.inwrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18
Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda
suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com
Attaching the source files once again.
Original Message Subject: Re: [WiX-users]
Referring to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From:
Suvrajyoti
Panda suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com CC: General
discussion about the WiX toolset.
wix-users@lists.sourceforge.netwix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program Files
(x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in section
'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to
TORTDEMO instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string' Value=''
KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(751) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(754) : error
Re: [WiX-users] Fwd: Re: Referring to fragments
to tweak the contents of this file.
Heat.exe can, with the correct arguments, give you
some generated code you can just plug into your
project and go. Probably. In theory. If the planets
are all in the correct alignments and you've made
the right sacrifices. In practice, you should
consider whether this kind of dynamic code
generation is really what you need.
Do the contents of that directory change without
warning or beyond your team's ability to keep up
with the changes? If so, then this kind of code
generation is potentially a way around the issue,
but ideally you should reconsider the application
design.
However, if this is more about generating code so
you don't have to crank it by hand, then I'd
recommend taking the generated code and adding the
missing or incorrect attributes (possibly with
PowerShell) and then take that code as source.
Further updates to this code can be done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda
suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in wrote:
Hi John,
Any updates on the below issue. I am still
stuck there.
Regards,
Suvra Jyoti
Original Message
Subject:Fwd: Re: [WiX-users] Referring to
fragments
Date: Mon, 18 Nov 2013 15:06:38 +0530
From: Suvrajyoti Panda
suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in
To: John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com
Attaching the source files once again.
Original Message
Subject:Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 15:04:31 +0530
From: Suvrajyoti Panda
suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in
To: John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com
CC: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
mailto:wix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error
C:\Program Files (x86)\WiX Toolset
v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol
'Component:TORTDEMO' in section 'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i
changed the name to TORTDEMO instead of
cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]'
Type='string' Value='' KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset
v3.7\bin\trunkdb.wxs(751) : error LGHT0103 :
The system cannot find the file
'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset
v3.7\bin\trunkdb.wxs(754) : error LGHT0103 :
The system cannot find the file
'SourceDir\tortoptions.v3.db'.
C:\Program Files (x86)\WiX Toolset
v3.7\bin\trunkdb.wxs(757) : error LGHT0103 :
The system cannot find the file
'SourceDir\tortoptions.v4.db'.
C:\Program Files (x86)\WiX Toolset
v3.7\bin\trunkdb.wxs(760) : error LGHT0103 :
The system cannot find the file
'SourceDir\tortoptions.v5.db'.
C:\Program Files (x86)\WiX Toolset
v3.7\bin\trunkdb.wxs(763
Re: [WiX-users] Fwd: Re: Referring to fragments
...@contata.co.in
wrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon,
18 Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda
suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com
Attaching the source files once again.
Original Message Subject: Re: [WiX-users]
Referring to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From:
Suvrajyoti
Panda suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John
Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com CC: General
discussion about the WiX toolset.
wix-users@lists.sourceforge.netwix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program Files
(x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in section
'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to
TORTDEMO instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string' Value=''
KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(751) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(754) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v3.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(757) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v4.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(760) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v5.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(763) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortosedata.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(766) : error
LGHT0103 :
Please suggest on the same.
On 18-11-2013 14:24, John Ludlow wrote:
Ah, I missed that.
You need to create a reference in your feature to each component,
because now you have components which aren't assigned to any feature,
which
means they would never be installed.
Please try this:
1. On your Heat.exe call, specify the -cg argument with a component
name:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag
-dr TORTDEMO -out trunkdb.wxs.
This should add a component group with all the components in the
output. The ID should be trunkdb, which you can reference in your
Feature.
2. Change your Feature element like so:
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
ComponentGroupRef Id='trunkdb'/
/Feature
This should reference the component group created in Step #1,
drawing all those components into that feature.
At first glance, the registry entry you've created looks fine. I'd
probably specify a value, but that's just me.
On 18 November 2013 08:32, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Hi John,
Please also have a look at the directory structure and registry
entry i am creating. Let me know in case i need a change there as well.
Regards,
Suvra Jyoti
Original Message Subject: Re: [WiX-users]
Referring to fragments Date: Mon, 18 Nov 2013 13:47:44 +0530 From:
Suvrajyoti Panda suvrajyo...@contata.co.insuvrajyo...@contata.co.in
To:
General discussion about the WiX toolset.
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net,
john.ludlow...@gmail.com
Hi John,
Thanks for the clarifications. I have come in in the morning and
tried to follow the steps as u have suggested. Attaching my two source
files
for your reference.
Below is what i have tried to do today:
- I have created the file trunkdb.wxs using the following
command:heat dir D:\Project\ESI\Code\trunk\
db -gg -sfrag -dr TORTDEMO -out trunkdb.wxs.
So the file generated looks like the below snippet: Wix xmlns=
http://schemas.microsoft.com/wix/2006/wi;http://schemas.microsoft.com/wix/2006/wi
Fragment
DirectoryRef Id=TORTDEMO
Directory Id=dir653F7E432DCA0892A253D0CEC7775D03
Name=db
Component
Id=cmp159DEBB341761ACFD08D530D4AB638B2
Guid={F89E44FD-879E-4076-B1A9-4CC2DFDB9DF4}
File
Id=fil13F4C3BF2526AB7CCACA852D90DAA880 KeyPath=yes
Re: [WiX-users] Fwd: Re: Referring to fragments
*). * The WIX installer that needs to be created should install the “db” directories that is created by the batch file. Basically i need to execute the installer when the scroipts for cruise control are fired. The firing of the cruisecontrol script fires the installer as well through a batch file. This is the approach that has been decided as of now. In case you other pointers do let me know specially the You will need to either specify the -var argument to heat.exe with a variable name (and tweak the value so that it matches correctly) or write some build code to tweak the contents of this file. if this helps. Moreover it is not that the error is being shown foll all the files in the db directory . It is showing for about 150 files in the db directory. There are a total of 379 files in the same. Regards, SuvraJyoti On 18-11-2013 19:00, John Ludlow wrote: Do those files exist at compilation time? They are C:\Program Files (x86) paths, and your code doesn't specify a full path in File/@Source. I'm not sure how it came up with that path, but it's probably wrong, since you are likely building your application binaries in a build area. You will need to either specify the -var argument to heat.exe with a variable name (and tweak the value so that it matches correctly) or write some build code to tweak the contents of this file. Heat.exe can, with the correct arguments, give you some generated code you can just plug into your project and go. Probably. In theory. If the planets are all in the correct alignments and you've made the right sacrifices. In practice, you should consider whether this kind of dynamic code generation is really what you need. Do the contents of that directory change without warning or beyond your team's ability to keep up with the changes? If so, then this kind of code generation is potentially a way around the issue, but ideally you should reconsider the application design. However, if this is more about generating code so you don't have to crank it by hand, then I'd recommend taking the generated code and adding the missing or incorrect attributes (possibly with PowerShell) and then take that code as source. Further updates to this code can be done by hand. Hope that helps On 18 November 2013 11:18, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Hi John, Any updates on the below issue. I am still stuck there. Regards, Suvra Jyoti Original Message Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in To: John Ludlow john.ludlow...@gmail.com mailto:john.ludlow...@gmail.com Attaching the source files once again. Original Message Subject: Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in To: John Ludlow john.ludlow...@gmail.com mailto:john.ludlow...@gmail.com CC: General
Re: [WiX-users] Fwd: Re: Referring to fragments
Do those files exist at compilation time? They are C:\Program Files (x86)
paths, and your code doesn't specify a full path in File/@Source. I'm not
sure how it came up with that path, but it's probably wrong, since you are
likely building your application binaries in a build area.
You will need to either specify the -var argument to heat.exe with a
variable name (and tweak the value so that it matches correctly) or write
some build code to tweak the contents of this file.
Heat.exe can, with the correct arguments, give you some generated code you
can just plug into your project and go. Probably. In theory. If the planets
are all in the correct alignments and you've made the right sacrifices. In
practice, you should consider whether this kind of dynamic code generation
is really what you need.
Do the contents of that directory change without warning or beyond your
team's ability to keep up with the changes? If so, then this kind of code
generation is potentially a way around the issue, but ideally you should
reconsider the application design.
However, if this is more about generating code so you don't have to crank
it by hand, then I'd recommend taking the generated code and adding the
missing or incorrect attributes (possibly with PowerShell) and then take
that code as source. Further updates to this code can be done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda suvrajyo...@contata.co.inwrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov
2013 15:06:38 +0530 From: Suvrajyoti Panda
suvrajyo...@contata.co.insuvrajyo...@contata.co.in To:
John Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com
Attaching the source files once again.
Original Message Subject: Re: [WiX-users] Referring to
fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From: Suvrajyoti Panda
suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John Ludlow
john.ludlow...@gmail.com john.ludlow...@gmail.com CC: General
discussion about the WiX toolset.
wix-users@lists.sourceforge.netwix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program Files (x86)\WiX
Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in section
'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to TORTDEMO
instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string' Value=''
KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below error.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(751) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v2.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(754) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v3.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(757) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v4.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(760) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortoptions.v5.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(763) : error
LGHT0103 :
The system cannot find the file 'SourceDir\tortosedata.db'.
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(766) : error
LGHT0103 :
Please suggest on the same.
On 18-11-2013 14:24, John Ludlow wrote:
Ah, I missed that.
You need to create a reference in your feature to each component,
because now you have components which aren't assigned to any feature, which
means they would never be installed.
Please try this:
1. On your Heat.exe call, specify the -cg argument with a component name:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag -dr
TORTDEMO -out trunkdb.wxs.
This should add a component group with all the components in the output.
The ID should be trunkdb, which you can reference in your Feature.
2. Change your Feature element like so:
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
ComponentGroupRef Id='trunkdb'/
/Feature
This should reference the component group created in Step #1, drawing
all those components into that feature.
At first glance, the registry entry you've created looks fine. I'd
probably specify a value, but that's just me.
On 18 November 2013 08:32, Suvrajyoti Panda suvrajyo
Re: [WiX-users] Fwd: Re: Referring to fragments
Hi John,
When I are created the trunkdb.wxs file i had ditected it to
D:\Project\ESI\Code\trunk\db. These files exist now also and are part of
the SVN source control. I do not get what you mean by C:\Program Files
(x86) and I'm not sure how it came up with that path . I am just
executing Light from the path C:\Program Files (x86)\WiX Toolset
v3.7\bin where in my two source files are also placed(tortenginedemo.wxs
and trunkdb.wxs). By File/@Source i guess you mean that as of now in the
fragment the path is only SourceDIr. Let me know how we can do that.
I need this to be dynamic in the sense that a batch file would execute
that would create the directory *db**(*D:\Project\ESI\Code\trunk\db*). *
The WIX installer that needs to be created should install the db
directories that is created by the batch file. Basically i need to
execute the installer when the scroipts for cruise control are fired.
The firing of the cruisecontrol script fires the installer as well
through a batch file.
This is the approach that has been decided as of now. In case you other
pointers do let me know specially the You will need to either specify
the -var argument to heat.exe with a variable name (and tweak the value
so that it matches correctly) or write some build code to tweak the
contents of this file. if this helps.
Moreover it is not that the error is being shown foll all the files in
the db directory . It is showing for about 150 files in the db
directory. There are a total of 379 files in the same.
Regards,
SuvraJyoti
On 18-11-2013 19:00, John Ludlow wrote:
Do those files exist at compilation time? They are C:\Program Files
(x86) paths, and your code doesn't specify a full path in
File/@Source. I'm not sure how it came up with that path, but it's
probably wrong, since you are likely building your application
binaries in a build area.
You will need to either specify the -var argument to heat.exe with a
variable name (and tweak the value so that it matches correctly) or
write some build code to tweak the contents of this file.
Heat.exe can, with the correct arguments, give you some generated code
you can just plug into your project and go. Probably. In theory. If
the planets are all in the correct alignments and you've made the
right sacrifices. In practice, you should consider whether this kind
of dynamic code generation is really what you need.
Do the contents of that directory change without warning or beyond
your team's ability to keep up with the changes? If so, then this kind
of code generation is potentially a way around the issue, but ideally
you should reconsider the application design.
However, if this is more about generating code so you don't have to
crank it by hand, then I'd recommend taking the generated code and
adding the missing or incorrect attributes (possibly with PowerShell)
and then take that code as source. Further updates to this code can be
done by hand.
Hope that helps
On 18 November 2013 11:18, Suvrajyoti Panda suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in wrote:
Hi John,
Any updates on the below issue. I am still stuck there.
Regards,
Suvra Jyoti
Original Message
Subject: Fwd: Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 15:06:38 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in
To: John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com
Attaching the source files once again.
Original Message
Subject: Re: [WiX-users] Referring to fragments
Date: Mon, 18 Nov 2013 15:04:31 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
mailto:suvrajyo...@contata.co.in
To: John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com
CC: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
mailto:wix-users@lists.sourceforge.net
Hi John,
I did as you suggested. I was getting the error C:\Program Files
(x86)\WiX Toolset v3.7\bin\TortEngineDemo.wxs(24) : error LGHT0
094 : Unresolved reference to symbol 'Component:TORTDEMO' in
section 'Product:{5
A1581BE-27C3-46A1-8699-4F1D642C97E0}'. So i changed the name to
TORTDEMO instead of cmpTrunkDB earlier as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=*TORTDEMO*
Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16
RemoveFolder Id='TORTDEMO' On='uninstall' /
RegistryValue Root='HKCU'
Key='Software\[Manufacturer]\[ProductName]' Type='string' Value=''
KeyPath='yes' /
/Component
/Directory
/Directory
/Directory
Now i am getting the below
Re: [WiX-users] Fwd: Re: Referring to fragments
Yeah I didn't explain that path thing very well. I was referring to this path: C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs This probably shouldn't be here. Best to keep this out of the WiX install directory. If this is a file which is generated for every build, then either use an intermediates folder in your build tree, or put it into the %tmp% directory. This is probably because you're not specifying a full path for the -out parameter. I'm not entirely clear on why you're launching an installer from CruiseControl - that seems a little weird to me. It sounds like you're trying to use MSI to achieve a continuous deployment scenario, and it's not really designed for that - is that what you're trying to do? I've not actually used the heat -var argument, so the advice I can give you will be limited. However, I believe that if you add -var:TrunkDbRootDir to your heat command, it will generate something like this: File Source=$(var.TrunkDbRootDir)\file.ext/ You will have to define that variable elsewhere, and it's up to you to make sure that it points to the correct place so that the path is correct when the variable is resolved. Someone with more experience of heat.exe might be able to help you further. Hope that helps On 18 November 2013 14:36, Suvrajyoti Panda suvrajyo...@contata.co.inwrote: Hi John, When I are created the trunkdb.wxs file i had ditected it to D:\Project\ESI\Code\trunk\db. These files exist now also and are part of the SVN source control. I do not get what you mean by C:\Program Files (x86) and I'm not sure how it came up with that path . I am just executing Light from the path C:\Program Files (x86)\WiX Toolset v3.7\bin where in my two source files are also placed(tortenginedemo.wxs and trunkdb.wxs). By File/@Source i guess you mean that as of now in the fragment the path is only SourceDIr. Let me know how we can do that. I need this to be dynamic in the sense that a batch file would execute that would create the directory *db** (*D:\Project\ESI\Code\trunk\db*). *The WIX installer that needs to be created should install the “db” directories that is created by the batch file. Basically i need to execute the installer when the scroipts for cruise control are fired. The firing of the cruisecontrol script fires the installer as well through a batch file. This is the approach that has been decided as of now. In case you other pointers do let me know specially the You will need to either specify the -var argument to heat.exe with a variable name (and tweak the value so that it matches correctly) or write some build code to tweak the contents of this file. if this helps. Moreover it is not that the error is being shown foll all the files in the db directory . It is showing for about 150 files in the db directory. There are a total of 379 files in the same. Regards, SuvraJyoti On 18-11-2013 19:00, John Ludlow wrote: Do those files exist at compilation time? They are C:\Program Files (x86) paths, and your code doesn't specify a full path in File/@Source. I'm not sure how it came up with that path, but it's probably wrong, since you are likely building your application binaries in a build area. You will need to either specify the -var argument to heat.exe with a variable name (and tweak the value so that it matches correctly) or write some build code to tweak the contents of this file. Heat.exe can, with the correct arguments, give you some generated code you can just plug into your project and go. Probably. In theory. If the planets are all in the correct alignments and you've made the right sacrifices. In practice, you should consider whether this kind of dynamic code generation is really what you need. Do the contents of that directory change without warning or beyond your team's ability to keep up with the changes? If so, then this kind of code generation is potentially a way around the issue, but ideally you should reconsider the application design. However, if this is more about generating code so you don't have to crank it by hand, then I'd recommend taking the generated code and adding the missing or incorrect attributes (possibly with PowerShell) and then take that code as source. Further updates to this code can be done by hand. Hope that helps On 18 November 2013 11:18, Suvrajyoti Panda suvrajyo...@contata.co.inwrote: Hi John, Any updates on the below issue. I am still stuck there. Regards, Suvra Jyoti Original Message Subject: Fwd: Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov 2013 15:06:38 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in suvrajyo...@contata.co.in To: John Ludlow john.ludlow...@gmail.com john.ludlow...@gmail.com Attaching the source files once again. Original Message Subject: Re: [WiX-users] Referring to fragments Date: Mon, 18 Nov 2013 15:04:31 +0530 From: Suvrajyoti Panda suvrajyo
