[WiX-users] Please unregister me
Hi, Please unregister me from this group. Regards, Suvra Jyoti Panda -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Hi Bevan, As suggested I did the following: * Replaced all the manually generated GUID's with * except the component preferences file as light was giving error for the same saying it is not allowed because the component is not nested under a directory. * Regarding the registry entries, it is as per the requirement. * I have performed the installation on a different machine, i have tried installing to a different path altogether as well. For instance i have tried doing the installation to C:\Energy Solutions International\PipelineOptimizer 6.0.0 and also to C:\Energy Solutions International\PipelineOptimizer 6.0.0 Test as is my requirement. Below are the observations: * All the folders data,db,gui,engine,security still are not removed. As per my requirement only the data folder should have stayed as i had set the permanent attributes for the component to yes using XSLT transform while harvesting. * All the registry entries got deleted, the registry entry for the data directory should have stayed. * Also commented out the registry entries then tried to see if there is any change, but still the same results * Also getting the same message in the log file: Disallowing uninstallation of component. Has it something to do with the remembering of the installation folder as suggested by Phil Hogland? Regards, Suvra Jyoti On 26-03-2014 00:44, Bevan Weiss wrote: I would suggest the following: Replace all manually generated GUIDs with '*' wherever possible. WiX can autogenerate GUIDs for you in most situations (where you have a source file I believe, it possibly works with RegistryKeys as well.. I can't remember). You've also got duplicated RegistryKey entries.. you have two entries, each with the same name and path, but just with Win64 set differently. Since any one particular .MSI can only be EITHER 32bit/64bit you shouldn't really have both like that. I believe most people are even moving away from labelling individual components Win64, and are just using the appropriate arch flag to the WiX tools at compile-time. I tend to just use the higher package level setting (which again I can't remember off the top of my head). You will need to perform an installation on a completely fresh machine. If this works, then it's not a problem with the installer, but with your machines configuration. Perhaps you changed around components etc resulting in a component having been installed at a previous time and not removed (if you ever did a minor upgrade, where the UPGRADE code stays the same, but the PRODUCT code changes and you haven't indicated that MajorUpgrades are to be performed). Try the fresh VM / PC install and uninstall and let us know the results. Bevan = Date: Tue, 25 Mar 2014 20:09:19 +0530 From: Suvrajyoti Pandasuvrajyo...@contata.co.in Subject: Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue To:wix-users@lists.sourceforge.net Hi Bevan, I have modified my source file as below. In the custom dialogs that i am using i have disabled the edit control that shows C:\Energy Solution International path(that part is not attached here). That's the way i thought of restricting the user and in the next dialog i am allowing the user to change the folder that is mapped to [MYFOLDER] property. Product Id=* Name=$(var.pgmName) Language=1033 Version=$(var.SvnVersionBuild) Manufacturer='$(var.ManufacturerName)' UpgradeCode=C54B7D5D-0E66-43E8-A770-C9750693F057 Package Id=* Keywords=Installer Description=Installer 1.0 Comments='Installer' InstallerVersion='300' Languages='1033' Compressed='yes' SummaryCodepage='1252' InstallScope='perMachine' Platform='x64'/ WixVariable Id=WixUILicenseRtf Value=$(var.LicensePath) / Media Id='1' Cabinet='Tort.cab' EmbedCab='yes' DiskPrompt=CD-ROM #1/ Property Id='DiskPrompt' Value=Tort Installation [1] / Directory Id='TARGETDIR' Name='SourceDir' Directory Id =DESTINATIONDIR Name=. /Directory Directory Id='ENERGYSOLUTIONS' Directory Id='TORT' Name='.' Component Id=x86RegEntPLODbPath Guid=A407D5B4-61F5-4CD6-8E76-3BD1C3949FE9 Win64=no RegistryValue Id=x86DbPathRegValue Root=HKLM Key=SOFTWARE\$(var.RegKeyEntry) Name=$(var.dbRegName) Value=[TORT]$(var.DBFolder) Type=string / /Component Component Id=x64RegEntPLODbPath Guid=56AE5376-4855-4C06-BB85-F669BB0C83F4 Win64=yes RegistryValue Id=x64DbPathRegValue Root=HKLM Key=SOFTWARE\$(var.RegKeyEntry) Name=$(var.dbRegName) Value=[TORT]$(var.DBFolder) Type=string / /Component Component Id=x86RegEntPLODataPath
[WiX-users] Fwd: Fwd: Re: Uninstall removing the default Virtual directory and not the one user created
Hi All,
I was able to resolve the issue by following the below structure:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ENERGYSOLUTIONS Name=.
Directory Id='InstallDir' Name=$(var.installDir)
Directory Id=MYWEBWEBSITE Name=$(var.websiteDir)
Component Id=VirtDirKey Guid=* Win64=yes
RegistryValue Root=HKLM
Key=SOFTWARE\$(var.RegKeyEntry) Name=VirtDir Value=[VIRTDIR]
Type=string/
/Component
Component Id=AppPoolKey Guid=* Win64=yes
RegistryValue Root=HKLM
Key=SOFTWARE\$(var.RegKeyEntry) Name=AppPool Value=[APPPOOL]
Type=string/
/Component
/Directory
/Directory
/Directory
/Directory
Property Id=VIRTUAL_DIR_VAL Value=PFWServiceApplication
Secure=yes
RegistrySearch Id=S.VIRTDIR Root=HKLM
Key=SOFTWARE\$(var.RegKeyEntry) Name=VirtDir Type=raw Win64=yes/
/Property
Property Id=WEB_APP_NAME Value=PFWServiceApplication
Secure=yes
RegistrySearch Id=S.APPPOOL Root=HKLM
Key=SOFTWARE\$(var.RegKeyEntry) Name=AppPool Type=raw Win64=yes/
/Property
Property Id=VIRTDIR Secure=yes
/Property
Property Id=APPPOOL Secure=yes
/Property
SetProperty Id=VIRTDIR Value=[VIRTUAL_DIR_VAL]
After=AppSearch/SetProperty
SetProperty Id=APPPOOL Value=[WEB_APP_NAME]
After=AppSearch/SetProperty
The following site is also good: http://www.nichesoftware.co.nz/node/633
Regards,
Suvra Jyoti
Original Message
Subject:[WiX-users] Fwd: Re: Uninstall removing the default Virtual
directory and not the one user created
Date: Tue, 25 Mar 2014 15:25:42 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
Reply-To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi David,
I have modified the WIX source file as below:
Property Id=VIRTDIR Secure=yes
RegistrySearch Id=RememberVirtDirProp Root=HKLM
Key='SOFTWARE\Test\DemoRememberVirtDir' Type='raw'
Name='Remembered'/RegistrySearch
/Property
SetDirectory Id=ENERGYSOLUTIONS
Value=[WindowsVolume]$(var.rootFolder)/
Feature Id=Complete Title=Pipeline Framework Service
Application Level=1 Display=expand
ConfigurableDirectory=MYWEBWEBSITE
Feature Id=MainContent Title=Pipeline Framework
Service Description=The website content Level=1
ComponentGroupRef Id=MyWebIssConfiguration /
ComponentGroupRef Id=MyWebWebComponents /
/Feature
Component Directory=TARGETDIR Win64=yes
RegistryValue Root='HKLM'
Key='SOFTWARE\Test\DemoRememberVirtDir' Name='Remembered'
Value='[VIRTUAL_DIR_VAL]' Type='string' /
RemoveFolder Id='CleanupApplicationFolder'
On='uninstall' /
/Component
/Feature
Property Id=FRAMEWORKBASEPATH
RegistrySearch Id=FindFrameworkDir Root=HKLM
Key=SOFTWARE\Microsoft\.NETFramework Name=InstallRoot Type=raw/
/Property
Property Id=ASPNETREGIIS
DirectorySearch Path=[FRAMEWORKBASEPATH] Depth=4
Id=FindAspNetRegIis
FileSearch Name=aspnet_regiis.exe MinVersion=4.0.0/
/DirectorySearch
/Property
!-- Switch ASP.NET to version 4.0 --
CustomAction Id=MakeWepApp40 Execute=deferred
Impersonate=no Directory=MYWEBWEBSITE ExeCommand=[ASPNETREGIIS]
-norestart -s W3SVC/1/ROOT/[WEB_APP_NAME] Return=check
Not Installed
/CustomAction
InstallExecuteSequence
Custom Action=MakeWepApp40
Before=InstallFinalizeASPNETREGIIS AND NOT Installed/Custom
/InstallExecuteSequence
UIRef Id=MyWebUI /
/Product
The [VIRTUAL_DIR_VAL] property is defined in another Wxi template file
as below:
Property Id=VIRTUAL_DIR_VAL Value=PFWServiceApplication Secure=yes
In the source file that has the dialogs i have used the
[VIRTUAL_DIR_VAL] property as below:
Control Id=VirtualDirEdit Type=Edit X=45 Y=85 Width=220
Height=18 Property=VIRTUAL_DIR_VAL Indirect=no Text={80} /
The issue is that if i change the virtual directory value to something
like PFWServiceApplication Test in the UI, then while installing i am
getting the error as highlighted below:
Action 15:08:40: MakeWepApp40.
MSI (s) (78:9C) [15:08:40:779]: Executing op:
CustomActionSchedule(Action=MakeWepApp40,ActionType=3106,Source=C:\Energy
Solutions
International\PipelineFrameworkService\PFWwebsite\,Target=C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe
-norestart -s W3SVC/1/ROOT/PFWServiceApplication,)
CustomAction MakeWepApp40 returned actual error code 1 (note this may
not be 100% accurate if translation happened inside sandbox)
MSI (s) (78:9C) [15:08:41:402]: Note: 1: 1722 2
Re: [WiX-users] Uninstall removing the default Virtual directory and not the one user created
Thanks David, I will try this and let you know
On 21-03-2014 19:48, David Watson wrote:
You need to persist the VIRTUAL_DIR_VAL (store it in the registry) so the
uninstaller knows it has changed otherwise it will use the default values.
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: 21 March 2014 12:53
To: General discussion about the WiX toolset.
Subject: [WiX-users] Uninstall removing the default Virtual directory and not
the one user created
Hi All,
I am creating virtual directory through WIX installer. The installer
allows user to change the name of the virtual directory through a custom
UI dialogue. The default virtual directory is PFWServiceApplication. If
the user changes this to say PFWServiceApplication_Test then the correct
virtual directory is created and installation works fine. But the
uninstall removes the default virtual directory. For instance i had
created the default virtual directory PFWServiceApplication manually for
testing and then used the installer to create the
PFWServiceApplication_Test virtual directory. On uninstalling the
PFWServiceApplication gets fully removed and the for
PFWServiceApplication_Test only the node is left under the default
website. What i want is that on uninstall only that virtual directory
that i installed through the installer should be removed. Below is my code.
Fragment
?include ConfigurationInitialize.wxi ?
!-- Install to default web site --
iis:WebSite Id=DefaultWebSite Description='Default Web Site'
iis:WebAddress Id=AllUnassigned Port=80 /
/iis:WebSite
DirectoryRef Id=MYWEBWEBSITE
!-- Configuring app pool --
Component Id=MyWebAppPoolCmp
Guid={9413B3CA-4CF1-4E3C-8F13-4E48291A8E22} KeyPath=yes Permanent=no
iis:WebAppPool Id=MyWebAppPool Name=[WEB_APP_NAME]
ManagedRuntimeVersion=v4.0 ManagedPipelineMode=Integrated /
/Component
!-- Configure virtual dir --
Component Id=MyWebVirtualDirCmp
Guid={751DEB01-ECC1-48ff-869A-65BCEE9E0528} KeyPath=yes Permanent=no
iis:WebVirtualDir Id=MyWebVirtualDir
Alias=[VIRTUAL_DIR_VAL] Directory=MYWEBWEBSITE WebSite=DefaultWebSite
iis:WebDirProperties Id=MyWebVirtDirProperties
AnonymousAccess=yes BasicAuthentication=yes
WindowsAuthentication=yes /
iis:WebApplication Id=MyWebWebApplication
Name=[VIRTUAL_DIR_VAL] WebAppPool=MyWebAppPool /
/iis:WebVirtualDir
/Component
/DirectoryRef
ComponentGroup Id=MyWebIssConfiguration
ComponentRef Id=MyWebVirtualDirCmp /
ComponentRef Id=MyWebAppPoolCmp /
/ComponentGroup
/Fragment
The include file ConfigurationInitialize.wxi has below code:
Property Id=VIRTUAL_DIR_VAL Value=PFWServiceApplication
Secure=yes/
!-- +++ web app name properties initialize
--
Property Id=WEB_APP_NAME Value=PFWServiceApplication
Secure=yes/
Please provide some help on this.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.
This message has been scanned for malware by Websense. www.websense.com
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Learn Graph Databases
[WiX-users] Fwd: Re: Uninstall removing the default Virtual directory and not the one user created
Hi David,
I have modified the WIX source file as below:
Property Id=VIRTDIR Secure=yes
RegistrySearch Id=RememberVirtDirProp Root=HKLM
Key='SOFTWARE\Test\DemoRememberVirtDir' Type='raw'
Name='Remembered'/RegistrySearch
/Property
SetDirectory Id=ENERGYSOLUTIONS
Value=[WindowsVolume]$(var.rootFolder)/
Feature Id=Complete Title=Pipeline Framework Service
Application Level=1 Display=expand
ConfigurableDirectory=MYWEBWEBSITE
Feature Id=MainContent Title=Pipeline Framework
Service Description=The website content Level=1
ComponentGroupRef Id=MyWebIssConfiguration /
ComponentGroupRef Id=MyWebWebComponents /
/Feature
Component Directory=TARGETDIR Win64=yes
RegistryValue Root='HKLM'
Key='SOFTWARE\Test\DemoRememberVirtDir' Name='Remembered'
Value='[VIRTUAL_DIR_VAL]' Type='string' /
RemoveFolder Id='CleanupApplicationFolder'
On='uninstall' /
/Component
/Feature
Property Id=FRAMEWORKBASEPATH
RegistrySearch Id=FindFrameworkDir Root=HKLM
Key=SOFTWARE\Microsoft\.NETFramework Name=InstallRoot Type=raw/
/Property
Property Id=ASPNETREGIIS
DirectorySearch Path=[FRAMEWORKBASEPATH] Depth=4
Id=FindAspNetRegIis
FileSearch Name=aspnet_regiis.exe MinVersion=4.0.0/
/DirectorySearch
/Property
!-- Switch ASP.NET to version 4.0 --
CustomAction Id=MakeWepApp40 Execute=deferred
Impersonate=no Directory=MYWEBWEBSITE ExeCommand=[ASPNETREGIIS]
-norestart -s W3SVC/1/ROOT/[WEB_APP_NAME] Return=check
Not Installed
/CustomAction
InstallExecuteSequence
Custom Action=MakeWepApp40
Before=InstallFinalizeASPNETREGIIS AND NOT Installed/Custom
/InstallExecuteSequence
UIRef Id=MyWebUI /
/Product
The [VIRTUAL_DIR_VAL] property is defined in another Wxi template file
as below:
Property Id=VIRTUAL_DIR_VAL Value=PFWServiceApplication Secure=yes
In the source file that has the dialogs i have used the
[VIRTUAL_DIR_VAL] property as below:
Control Id=VirtualDirEdit Type=Edit X=45 Y=85 Width=220
Height=18 Property=VIRTUAL_DIR_VAL Indirect=no Text={80} /
The issue is that if i change the virtual directory value to something
like PFWServiceApplication Test in the UI, then while installing i am
getting the error as highlighted below:
Action 15:08:40: MakeWepApp40.
MSI (s) (78:9C) [15:08:40:779]: Executing op:
CustomActionSchedule(Action=MakeWepApp40,ActionType=3106,Source=C:\Energy
Solutions
International\PipelineFrameworkService\PFWwebsite\,Target=C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe
-norestart -s W3SVC/1/ROOT/PFWServiceApplication,)
CustomAction MakeWepApp40 returned actual error code 1 (note this may
not be 100% accurate if translation happened inside sandbox)
MSI (s) (78:9C) [15:08:41:402]: Note: 1: 1722 2: MakeWepApp40 3:
C:\Energy Solutions International\PipelineFrameworkService\PFWwebsite\
4: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe
-norestart -s W3SVC/1/ROOT/PFWServiceApplication
Error 1722. There is a problem with this Windows Installer package*. A
program run as part of the setup did not finish as expected. Contact
your support personnel or package vendor. Action MakeWepApp40, location:
C:\Energy Solutions International\PipelineFrameworkService\PFWwebsite\*,
command: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe
-norestart -s W3SVC/1/ROOT/PFWServiceApplication
But if i do not change the virtual directory in the UI then there is no
issue and i can create the registry entry for remembering the virtual
directory value. Please let me know how i can solve this.
Regards,
Suvra Jyoti
Original Message
Subject:Re: [WiX-users] Uninstall removing the default Virtual
directory and not the one user created
Date: Tue, 25 Mar 2014 11:58:52 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
Reply-To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
To: wix-users@lists.sourceforge.net
Thanks David, I will try this and let you know
On 21-03-2014 19:48, David Watson wrote:
You need to persist the VIRTUAL_DIR_VAL (store it in the registry) so the
uninstaller knows it has changed otherwise it will use the default values.
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: 21 March 2014 12:53
To: General discussion about the WiX toolset.
Subject: [WiX-users] Uninstall removing the default Virtual directory and not
the one user created
Hi All,
I am creating virtual directory through WIX installer. The installer
allows user to change the name of the virtual directory through a custom
UI dialogue. The default virtual
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
a formatted string, so it might not work.
If it doesn't then you'll need to essentially do the same thing but using
some custom action to modify the runtime database.
If this doesn't work, then my suggestion would be that you give up.
If it's really that important then eventually they will hire someone that
will make it work ;)
Regards,
Bevan
Date: Wed, 19 Mar 2014 20:04:41 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
Subject: Re: [WiX-users] (Gentle Reminder)Creating directory under
C:\Programdata same as what the user specified in the UI dialogue
Hi Bevan,
Could you please provide some sample code on how to have a formatted string
as the folder names for these two items or the custom action thing.
Regards,
Suvra Jyoti
On 19-03-2014 17:37, Bevan Weiss wrote:
Suvrajyoti,
If you allow the INSTALLDIR to be changed, then the whole thing could
be different...
For instance if someone changed the INSTALLDIR to be C:\, then what do
you consider that the C:\ProgramData.. folder should be named?
I believe that you shouldn't allow the user to select any directory
they like.
Instead you should give them the option (via a customised gui page) of
adding on a suffix to the installer directory that you have already
hardcoded.
Then you can just have your two folders be:
C:\Program Files ()\{Manufacturer}\{Product Name} 06.00.00 {whatever
user suffix they want} And C:\ProgramData\{Manufacturer}\{Product
Name} 06.00.00 {whatever user suffix they want}
This is possibly do-able by just having a formatted string as the
folder names for these two items.
If that doesn't work due to a WiX limitation, then you should be able
to perform a custom action to modify the MSI in memory database early
on to get the tables right for the actual installer operation.
Regards,
Bevan Weiss
Date: Wed, 19 Mar 2014 13:57:28 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
Subject: Re: [WiX-users] (Gentle Reminder)Creating directory under
C:\Programdata same as what the user specified in the UI dialogue
Thanks for the elaborate explanation, it made things clearer. But the
current structure that i am trying to follow is something that has
been decided upon.
How would i parse the INSTALLDIR value after it's been changed in the
UI and isolate out the part that has changed, i mean is there some
sample code that you could provide me?
On 18-03-2014 22:12, Phil Wilson wrote:
If you look at the tutorial and my previous example there are just a
couple of principles here that you can use to figure out directories
in general:
1. The default installation folder must be a folder derived from
standard system folder properties such as [ProgramFilesFolder]. Not
only is that the correct default location, it is not hardcoded, it is
resolved at install time to the actual values, These folder
properties are automatically the right location, the right name for
non-English systems, and the right location for 32 or 64-bit systems.
So if you actually wanted to have some of your files in ProgramData
you would use [LocalAppDataFolder] as the root of the property you
use to construct your folder. The key here is that you use standard
properties to construct a property name that describes your actual
folder. Typically the default name for the main app folder is
INSTALLDIR, constructed from [ProgramFilesFolder] [Manufacturer]
[ProductName] and stick {ProductVersion] at the end if you like.
Similarly your ProgramData location could be called MYDATAFOLDER
constructed from [LocalAppDataFolder] {Manufacturer] [ProductName].
That also means, by the way, that your [ProductName] should be
Pipeline Optimizer and your [Manufacturer] property should be Energy
Solutions, so you don't need to specify the hardcoded values
everywhere. See Name and Manufacturer in the Product element.
2. When the actual paths are constructed from properties, they are
automatically changed to reflect the user's choioce (if any) and the
actual paths on the system. That means that for your copyfile you
always do the copy from (for example) [SourceDir] to [INSTALLDIR] and
it will always be correct. Or it could be from [SourceDir] to
[MYDATAFOLDER] and it will always be correct. The main install folder
[INSTALLDIR] (that can be altered) is nothing to do with the
LocalAppDataFolder location, which is usually a fixed directory with
your manufacturer and product name in it.
Having said that, and assuming I understand what you're trying to do,
I know of no built-in way to construct a custom ProgramData location
based on a UI change of INSTALLDIR. You would need to write code to
parse the INSTALLDIR value after it's been changed in the UI and
isolate out the part that has changed, and then set the property
MYDATAFOLDER to be [LocallAppDataFolder] plus whatever you parsed out
from INSTALLDIR. Your copyfile is still [SourceDir] to [MYDATAFOLDER].
If it's the app that requires the unusual install
[WiX-users] Uninstall removing the default Virtual directory and not the one user created
Hi All,
I am creating virtual directory through WIX installer. The installer
allows user to change the name of the virtual directory through a custom
UI dialogue. The default virtual directory is PFWServiceApplication. If
the user changes this to say PFWServiceApplication_Test then the correct
virtual directory is created and installation works fine. But the
uninstall removes the default virtual directory. For instance i had
created the default virtual directory PFWServiceApplication manually for
testing and then used the installer to create the
PFWServiceApplication_Test virtual directory. On uninstalling the
PFWServiceApplication gets fully removed and the for
PFWServiceApplication_Test only the node is left under the default
website. What i want is that on uninstall only that virtual directory
that i installed through the installer should be removed. Below is my code.
Fragment
?include ConfigurationInitialize.wxi ?
!-- Install to default web site --
iis:WebSite Id=DefaultWebSite Description='Default Web Site'
iis:WebAddress Id=AllUnassigned Port=80 /
/iis:WebSite
DirectoryRef Id=MYWEBWEBSITE
!-- Configuring app pool --
Component Id=MyWebAppPoolCmp
Guid={9413B3CA-4CF1-4E3C-8F13-4E48291A8E22} KeyPath=yes Permanent=no
iis:WebAppPool Id=MyWebAppPool Name=[WEB_APP_NAME]
ManagedRuntimeVersion=v4.0 ManagedPipelineMode=Integrated /
/Component
!-- Configure virtual dir --
Component Id=MyWebVirtualDirCmp
Guid={751DEB01-ECC1-48ff-869A-65BCEE9E0528} KeyPath=yes Permanent=no
iis:WebVirtualDir Id=MyWebVirtualDir
Alias=[VIRTUAL_DIR_VAL] Directory=MYWEBWEBSITE WebSite=DefaultWebSite
iis:WebDirProperties Id=MyWebVirtDirProperties
AnonymousAccess=yes BasicAuthentication=yes
WindowsAuthentication=yes /
iis:WebApplication Id=MyWebWebApplication
Name=[VIRTUAL_DIR_VAL] WebAppPool=MyWebAppPool /
/iis:WebVirtualDir
/Component
/DirectoryRef
ComponentGroup Id=MyWebIssConfiguration
ComponentRef Id=MyWebVirtualDirCmp /
ComponentRef Id=MyWebAppPoolCmp /
/ComponentGroup
/Fragment
The include file ConfigurationInitialize.wxi has below code:
Property Id=VIRTUAL_DIR_VAL Value=PFWServiceApplication
Secure=yes/
!-- +++ web app name properties initialize
--
Property Id=WEB_APP_NAME Value=PFWServiceApplication
Secure=yes/
Please provide some help on this.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Thanks for the elaborate explanation, it made things clearer. But the
current structure that i am trying to follow is something that has been
decided upon.
How would i parse the INSTALLDIR value after it's been changed in the UI
and isolate out the part that has changed, i mean is there some sample
code that you could provide me?
On 18-03-2014 22:12, Phil Wilson wrote:
If you look at the tutorial and my previous example there are just a
couple of principles here that you can use to figure out directories
in general:
1. The default installation folder must be a folder derived from
standard system folder properties such as [ProgramFilesFolder]. Not
only is that the correct default location, it is not hardcoded, it is
resolved at install time to the actual values, These folder properties
are automatically the right location, the right name for non-English
systems, and the right location for 32 or 64-bit systems. So if you
actually wanted to have some of your files in ProgramData you would
use [LocalAppDataFolder] as the root of the property you use to
construct your folder. The key here is that you use standard
properties to construct a property name that describes your actual
folder. Typically the default name for the main app folder is
INSTALLDIR, constructed from [ProgramFilesFolder] [Manufacturer]
[ProductName] and stick {ProductVersion] at the end if you like.
Similarly your ProgramData location could be called MYDATAFOLDER
constructed from [LocalAppDataFolder] {Manufacturer] [ProductName].
That also means, by the way, that your [ProductName] should be
Pipeline Optimizer and your [Manufacturer] property should be Energy
Solutions, so you don't need to specify the hardcoded values
everywhere. See Name and Manufacturer in the Product element.
2. When the actual paths are constructed from properties, they are
automatically changed to reflect the user's choioce (if any) and the
actual paths on the system. That means that for your copyfile you
always do the copy from (for example) [SourceDir] to [INSTALLDIR] and
it will always be correct. Or it could be from [SourceDir] to
[MYDATAFOLDER] and it will always be correct. The main install folder
[INSTALLDIR] (that can be altered) is nothing to do with the
LocalAppDataFolder location, which is usually a fixed directory with
your manufacturer and product name in it.
Having said that, and assuming I understand what you're trying to do,
I know of no built-in way to construct a custom ProgramData location
based on a UI change of INSTALLDIR. You would need to write code to
parse the INSTALLDIR value after it's been changed in the UI and
isolate out the part that has changed, and then set the property
MYDATAFOLDER to be [LocallAppDataFolder] plus whatever you parsed out
from INSTALLDIR. Your copyfile is still [SourceDir] to [MYDATAFOLDER].
If it's the app that requires the unusual install folder and the
variable preferences file location, it's rather unusual, that's why
it's making your setup require a bunch of extra work. If you've
invented some of this, you should reconsider.
---
Phil Wilson
On Tue, Mar 18, 2014 at 5:54 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Thanks Walter for the response.
I too understand that this is not conventional and may be not right but
when i am installing the tha pplication it creates a directory C:\Energy
Solutions International\PipelineOptimizer 06.00.00\gui that has an
application mosquito.exe that requires this preferences.xml file under
the C:\ProgramData\Energy Solutions International itself else it is
showing the error Preferences.xml not found. Thats the reason i am
using the CopyFile the way I am.
On 18-03-2014 17:22, Walter Dexter wrote:
I understand what you're trying to do, but please stop and ask if it makes
sense.
The format of the path under ProgramData is usually
publisher/software/files and not editable by the user.
For that matter, the software should be under Program Files, referenced by
symbol, not C:\.
It's a bit confusing when you say you're trying to create a directory
using copyfile because that's not you create directories. It's also
confusing that you have hardcoded the directory as the Program Files
folder. Typically you use the ProgramFilesFolder like this:
http://wix.tramontana.co.hu/tutorial/getting-started/the-files-inside
and the rest of that tutorial would probably help. Then your copyfile
doesn't refer to your hardcoded path, it does a copy from SourceDir to
INSTALLFOLDER, which is the property name for the install location
chosen by the user.
---
Phil Wilson
On Thu, Mar 13, 2014 at 6:43 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Guys, Please let me know if some one has any idea on the below problem.
Original Message
Subject:Creating directory under C:\Programdata same as what the
user
specified in the UI dialogue
Date: Thu, 13
[WiX-users] (Ignore earlier mail)Re: (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Thanks Phil, for the elaborate explanation, it made things clearer. But
the current structure that i am trying to follow is something that has
been decided upon.
How would i parse the INSTALLDIR value after it's been changed in the UI
and isolate out the part that has changed, i mean is there some sample
code that you could provide me?
Regards,
Suvra Jyoti
On 18-03-2014 22:12, Phil Wilson wrote:
If you look at the tutorial and my previous example there are just a
couple of principles here that you can use to figure out directories
in general:
1. The default installation folder must be a folder derived from
standard system folder properties such as [ProgramFilesFolder]. Not
only is that the correct default location, it is not hardcoded, it is
resolved at install time to the actual values, These folder properties
are automatically the right location, the right name for non-English
systems, and the right location for 32 or 64-bit systems. So if you
actually wanted to have some of your files in ProgramData you would
use [LocalAppDataFolder] as the root of the property you use to
construct your folder. The key here is that you use standard
properties to construct a property name that describes your actual
folder. Typically the default name for the main app folder is
INSTALLDIR, constructed from [ProgramFilesFolder] [Manufacturer]
[ProductName] and stick {ProductVersion] at the end if you like.
Similarly your ProgramData location could be called MYDATAFOLDER
constructed from [LocalAppDataFolder] {Manufacturer] [ProductName].
That also means, by the way, that your [ProductName] should be
Pipeline Optimizer and your [Manufacturer] property should be Energy
Solutions, so you don't need to specify the hardcoded values
everywhere. See Name and Manufacturer in the Product element.
2. When the actual paths are constructed from properties, they are
automatically changed to reflect the user's choioce (if any) and the
actual paths on the system. That means that for your copyfile you
always do the copy from (for example) [SourceDir] to [INSTALLDIR] and
it will always be correct. Or it could be from [SourceDir] to
[MYDATAFOLDER] and it will always be correct. The main install folder
[INSTALLDIR] (that can be altered) is nothing to do with the
LocalAppDataFolder location, which is usually a fixed directory with
your manufacturer and product name in it.
Having said that, and assuming I understand what you're trying to do,
I know of no built-in way to construct a custom ProgramData location
based on a UI change of INSTALLDIR. You would need to write code to
parse the INSTALLDIR value after it's been changed in the UI and
isolate out the part that has changed, and then set the property
MYDATAFOLDER to be [LocallAppDataFolder] plus whatever you parsed out
from INSTALLDIR. Your copyfile is still [SourceDir] to [MYDATAFOLDER].
If it's the app that requires the unusual install folder and the
variable preferences file location, it's rather unusual, that's why
it's making your setup require a bunch of extra work. If you've
invented some of this, you should reconsider.
---
Phil Wilson
On Tue, Mar 18, 2014 at 5:54 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Thanks Walter for the response.
I too understand that this is not conventional and may be not right but
when i am installing the tha pplication it creates a directory C:\Energy
Solutions International\PipelineOptimizer 06.00.00\gui that has an
application mosquito.exe that requires this preferences.xml file under
the C:\ProgramData\Energy Solutions International itself else it is
showing the error Preferences.xml not found. Thats the reason i am
using the CopyFile the way I am.
On 18-03-2014 17:22, Walter Dexter wrote:
I understand what you're trying to do, but please stop and ask if it makes
sense.
The format of the path under ProgramData is usually
publisher/software/files and not editable by the user.
For that matter, the software should be under Program Files, referenced by
symbol, not C:\.
It's a bit confusing when you say you're trying to create a directory
using copyfile because that's not you create directories. It's also
confusing that you have hardcoded the directory as the Program Files
folder. Typically you use the ProgramFilesFolder like this:
http://wix.tramontana.co.hu/tutorial/getting-started/the-files-inside
and the rest of that tutorial would probably help. Then your copyfile
doesn't refer to your hardcoded path, it does a copy from SourceDir to
INSTALLFOLDER, which is the property name for the install location
chosen by the user.
---
Phil Wilson
On Thu, Mar 13, 2014 at 6:43 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Guys, Please let me know if some one has any idea on the below problem.
Original Message
Subject:Creating directory under C:\Programdata same as what the
user
specified in the UI
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Hey Walter,
As of now no, i do not have that option.
Regards,
Suvra Jyoti
On 19-03-2014 17:27, Walter Dexter wrote:
Do you have the option to disallow install directory being changed? Seems
like a lot of software is doing that lately.
On Mar 18, 2014 8:03 AM, Suvrajyoti Panda suvrajyo...@contata.co.in
wrote:
Thanks Walter for the response.
I too understand that this is not conventional and may be not right but
when i am installing the tha pplication it creates a directory C:\Energy
Solutions International\PipelineOptimizer 06.00.00\gui that has an
application mosquito.exe that requires this preferences.xml file under
the C:\ProgramData\Energy Solutions International itself else it is
showing the error Preferences.xml not found. Thats the reason i am
using the CopyFile the way I am.
On 18-03-2014 17:22, Walter Dexter wrote:
I understand what you're trying to do, but please stop and ask if it
makes
sense.
The format of the path under ProgramData is usually
publisher/software/files and not editable by the user.
For that matter, the software should be under Program Files, referenced
by
symbol, not C:\.
It's a bit confusing when you say you're trying to create a directory
using copyfile because that's not you create directories. It's also
confusing that you have hardcoded the directory as the Program Files
folder. Typically you use the ProgramFilesFolder like this:
http://wix.tramontana.co.hu/tutorial/getting-started/the-files-inside
and the rest of that tutorial would probably help. Then your copyfile
doesn't refer to your hardcoded path, it does a copy from SourceDir to
INSTALLFOLDER, which is the property name for the install location
chosen by the user.
---
Phil Wilson
On Thu, Mar 13, 2014 at 6:43 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Guys, Please let me know if some one has any idea on the below problem.
Original Message
Subject:Creating directory under C:\Programdata same as what the
user
specified in the UI dialogue
Date: Thu, 13 Mar 2014 10:37:13 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I had appended this query in another topic, so reposting the same under
different heading.
I have this requirement in which i want to create directory under
C:\Programdata same as what the user specified in the UI dialogue .I am
trying to do that using CopyFile. Below is the code:
Property Id=CopyDestination Value=C:\ProgramData\Energy Solutions
International\PipelineOptimizer $(var.SvnVersion)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer
$(var.SvnVersion)'
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
SetDirectory Id=EnergySolutions Value=C:\Energy Solutions
International/
Property Id=WIXUI_INSTALLDIR Value=TORT /
UIRef Id=WixUI_InstallDir /
While doing the installation if the user changes the install directory
from the one that is default(it comes out as PipelineOptimizer 06.00.00)
to some other name, the file being copied using the CopyFile attribute
is still copied to the same directory under the programdata as the one
which is defaulted in the UI which is to C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00. What i want though is that if
the user changes the directory to say PipelineOptimizer 06.00.00 Test,
then the file should be copied to the C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00 Test but this does not happen.
Is there a way i can achieve the same. I tried using custom action to
set the property CopyDestination but was not able to do so. Please let
me know if there is a solution to this if possible with some sample
code.
Also is there a way in which we can create 2 prompts to the user during
install. This would allow us to use the directory variable independent
of the path so that we can use this approach for the ProgramData
subfolder .
i. Prompt 1: The install path. For example, the default path is
C:\Energy Solutions International\.
ii.Prompt 2: The install directory. For example, the default
directory is PipelineOptimizer 06.00.00.
and then use the value of the install directory somehow to copy the file
to right location. Is the above approach possible? Please help as it is
urgent for me.
Regards,
Suvra Jyoti
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Hi Bevan,
Could you please provide some sample code on how to have a formatted
string as the folder names for these two items or the custom action thing.
Regards,
Suvra Jyoti
On 19-03-2014 17:37, Bevan Weiss wrote:
Suvrajyoti,
If you allow the INSTALLDIR to be changed, then the whole thing could be
different...
For instance if someone changed the INSTALLDIR to be C:\, then what do you
consider that the C:\ProgramData.. folder should be named?
I believe that you shouldn't allow the user to select any directory they
like.
Instead you should give them the option (via a customised gui page) of
adding on a suffix to the installer directory that you have already
hardcoded.
Then you can just have your two folders be:
C:\Program Files ()\{Manufacturer}\{Product Name} 06.00.00 {whatever user
suffix they want}
And
C:\ProgramData\{Manufacturer}\{Product Name} 06.00.00 {whatever user suffix
they want}
This is possibly do-able by just having a formatted string as the folder
names for these two items.
If that doesn't work due to a WiX limitation, then you should be able to
perform a custom action to modify the MSI in memory database early on to get
the tables right for the actual installer operation.
Regards,
Bevan Weiss
Date: Wed, 19 Mar 2014 13:57:28 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
Subject: Re: [WiX-users] (Gentle Reminder)Creating directory under
C:\Programdata same as what the user specified in the UI dialogue
Thanks for the elaborate explanation, it made things clearer. But the
current structure that i am trying to follow is something that has been
decided upon.
How would i parse the INSTALLDIR value after it's been changed in the UI and
isolate out the part that has changed, i mean is there some sample code that
you could provide me?
On 18-03-2014 22:12, Phil Wilson wrote:
If you look at the tutorial and my previous example there are just a
couple of principles here that you can use to figure out directories
in general:
1. The default installation folder must be a folder derived from
standard system folder properties such as [ProgramFilesFolder]. Not
only is that the correct default location, it is not hardcoded, it is
resolved at install time to the actual values, These folder properties
are automatically the right location, the right name for non-English
systems, and the right location for 32 or 64-bit systems. So if you
actually wanted to have some of your files in ProgramData you would
use [LocalAppDataFolder] as the root of the property you use to
construct your folder. The key here is that you use standard
properties to construct a property name that describes your actual
folder. Typically the default name for the main app folder is
INSTALLDIR, constructed from [ProgramFilesFolder] [Manufacturer]
[ProductName] and stick {ProductVersion] at the end if you like.
Similarly your ProgramData location could be called MYDATAFOLDER
constructed from [LocalAppDataFolder] {Manufacturer] [ProductName].
That also means, by the way, that your [ProductName] should be
Pipeline Optimizer and your [Manufacturer] property should be Energy
Solutions, so you don't need to specify the hardcoded values
everywhere. See Name and Manufacturer in the Product element.
2. When the actual paths are constructed from properties, they are
automatically changed to reflect the user's choioce (if any) and the
actual paths on the system. That means that for your copyfile you
always do the copy from (for example) [SourceDir] to [INSTALLDIR] and
it will always be correct. Or it could be from [SourceDir] to
[MYDATAFOLDER] and it will always be correct. The main install folder
[INSTALLDIR] (that can be altered) is nothing to do with the
LocalAppDataFolder location, which is usually a fixed directory with
your manufacturer and product name in it.
Having said that, and assuming I understand what you're trying to do,
I know of no built-in way to construct a custom ProgramData location
based on a UI change of INSTALLDIR. You would need to write code to
parse the INSTALLDIR value after it's been changed in the UI and
isolate out the part that has changed, and then set the property
MYDATAFOLDER to be [LocallAppDataFolder] plus whatever you parsed out
from INSTALLDIR. Your copyfile is still [SourceDir] to [MYDATAFOLDER].
If it's the app that requires the unusual install folder and the
variable preferences file location, it's rather unusual, that's why
it's making your setup require a bunch of extra work. If you've
invented some of this, you should reconsider.
---
Phil Wilson
On Tue, Mar 18, 2014 at 5:54 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Thanks Walter for the response.
I too understand that this is not conventional and may be not right
but when i am installing the tha pplication it creates a directory
C:\Energy Solutions International\PipelineOptimizer 06.00.00\gui
that has an application
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Hi Phil,
Sorry,if my explanation of the requirement was not clear. What I am
trying to ask is specifically as below:
When i start installing the application using the installer, then in the
UI the default installation path is C:\Energy Solutions
International\PipelineOptimizer 06.00.00\, which is editable. I now edit
the path in the UI to say C:\Energy Solutions
International\PipelineOptimizer Test\. I want somehow to use this input
of PipelineOptimizer Test in the WIX source file so that i can
copy the file preferences.xml to a directory called PipelineOptimizer
Test under C:\ProgramData\Energy Solutions International. If i did not
edit the UI the default path where the file would get copied was
C:\ProgramData\Energy Solutions International\PipelineOptimizer 06.00.00.
Below is the screenshot if is the screenshot:
Attaching the screenshots if you are somehow not able to view.
Regards,
Suvra Jyoti
On 13-03-2014 22:11, Phil Wilson wrote:
It's a bit confusing when you say you're trying to create a directory
using copyfile because that's not you create directories. It's also
confusing that you have hardcoded the directory as the Program Files
folder. Typically you use the ProgramFilesFolder like this:
http://wix.tramontana.co.hu/tutorial/getting-started/the-files-inside
and the rest of that tutorial would probably help. Then your copyfile
doesn't refer to your hardcoded path, it does a copy from SourceDir to
INSTALLFOLDER, which is the property name for the install location
chosen by the user.
---
Phil Wilson
On Thu, Mar 13, 2014 at 6:43 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Guys, Please let me know if some one has any idea on the below problem.
Original Message
Subject:Creating directory under C:\Programdata same as what the user
specified in the UI dialogue
Date: Thu, 13 Mar 2014 10:37:13 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I had appended this query in another topic, so reposting the same under
different heading.
I have this requirement in which i want to create directory under
C:\Programdata same as what the user specified in the UI dialogue .I am
trying to do that using CopyFile. Below is the code:
Property Id=CopyDestination Value=C:\ProgramData\Energy Solutions
International\PipelineOptimizer $(var.SvnVersion)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer $(var.SvnVersion)'
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
SetDirectory Id=EnergySolutions Value=C:\Energy Solutions
International/
Property Id=WIXUI_INSTALLDIR Value=TORT /
UIRef Id=WixUI_InstallDir /
While doing the installation if the user changes the install directory
from the one that is default(it comes out as PipelineOptimizer 06.00.00)
to some other name, the file being copied using the CopyFile attribute
is still copied to the same directory under the programdata as the one
which is defaulted in the UI which is to C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00. What i want though is that if
the user changes the directory to say PipelineOptimizer 06.00.00 Test,
then the file should be copied to the C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00 Test but this does not happen.
Is there a way i can achieve the same. I tried using custom action to
set the property CopyDestination but was not able to do so. Please let
me know if there is a solution to this if possible with some sample code.
Also is there a way in which we can create 2 prompts to the user during
install. This would allow us to use the directory variable independent
of the path so that we can use this approach for the ProgramData subfolder .
i. Prompt 1: The install path. For example, the default path is
C:\Energy Solutions International\.
ii.Prompt 2: The install directory. For example, the default
directory is PipelineOptimizer 06.00.00.
and then use the value of the install directory somehow to copy the file
to right location. Is the above approach possible? Please help as it is
urgent for me.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http
Re: [WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Thanks Walter for the response.
I too understand that this is not conventional and may be not right but
when i am installing the tha pplication it creates a directory C:\Energy
Solutions International\PipelineOptimizer 06.00.00\gui that has an
application mosquito.exe that requires this preferences.xml file under
the C:\ProgramData\Energy Solutions International itself else it is
showing the error Preferences.xml not found. Thats the reason i am
using the CopyFile the way I am.
On 18-03-2014 17:22, Walter Dexter wrote:
I understand what you're trying to do, but please stop and ask if it makes
sense.
The format of the path under ProgramData is usually
publisher/software/files and not editable by the user.
For that matter, the software should be under Program Files, referenced by
symbol, not C:\.
It's a bit confusing when you say you're trying to create a directory
using copyfile because that's not you create directories. It's also
confusing that you have hardcoded the directory as the Program Files
folder. Typically you use the ProgramFilesFolder like this:
http://wix.tramontana.co.hu/tutorial/getting-started/the-files-inside
and the rest of that tutorial would probably help. Then your copyfile
doesn't refer to your hardcoded path, it does a copy from SourceDir to
INSTALLFOLDER, which is the property name for the install location
chosen by the user.
---
Phil Wilson
On Thu, Mar 13, 2014 at 6:43 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Guys, Please let me know if some one has any idea on the below problem.
Original Message
Subject:Creating directory under C:\Programdata same as what the
user
specified in the UI dialogue
Date: Thu, 13 Mar 2014 10:37:13 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I had appended this query in another topic, so reposting the same under
different heading.
I have this requirement in which i want to create directory under
C:\Programdata same as what the user specified in the UI dialogue .I am
trying to do that using CopyFile. Below is the code:
Property Id=CopyDestination Value=C:\ProgramData\Energy Solutions
International\PipelineOptimizer $(var.SvnVersion)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer $(var.SvnVersion)'
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
SetDirectory Id=EnergySolutions Value=C:\Energy Solutions
International/
Property Id=WIXUI_INSTALLDIR Value=TORT /
UIRef Id=WixUI_InstallDir /
While doing the installation if the user changes the install directory
from the one that is default(it comes out as PipelineOptimizer 06.00.00)
to some other name, the file being copied using the CopyFile attribute
is still copied to the same directory under the programdata as the one
which is defaulted in the UI which is to C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00. What i want though is that if
the user changes the directory to say PipelineOptimizer 06.00.00 Test,
then the file should be copied to the C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00 Test but this does not happen.
Is there a way i can achieve the same. I tried using custom action to
set the property CopyDestination but was not able to do so. Please let
me know if there is a solution to this if possible with some sample code.
Also is there a way in which we can create 2 prompts to the user during
install. This would allow us to use the directory variable independent
of the path so that we can use this approach for the ProgramData
subfolder .
i. Prompt 1: The install path. For example, the default path is
C:\Energy Solutions International\.
ii.Prompt 2: The install directory. For example, the default
directory is PipelineOptimizer 06.00.00.
and then use the value of the install directory somehow to copy the file
to right location. Is the above approach possible? Please help as it is
urgent for me.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
[WiX-users] (Gentle Reminder)Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Guys, Please let me know if some one has any idea on the below problem.
Original Message
Subject:Creating directory under C:\Programdata same as what the user
specified in the UI dialogue
Date: Thu, 13 Mar 2014 10:37:13 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I had appended this query in another topic, so reposting the same under
different heading.
I have this requirement in which i want to create directory under
C:\Programdata same as what the user specified in the UI dialogue .I am
trying to do that using CopyFile. Below is the code:
Property Id=CopyDestination Value=C:\ProgramData\Energy Solutions
International\PipelineOptimizer $(var.SvnVersion)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer $(var.SvnVersion)'
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
SetDirectory Id=EnergySolutions Value=C:\Energy Solutions
International/
Property Id=WIXUI_INSTALLDIR Value=TORT /
UIRef Id=WixUI_InstallDir /
While doing the installation if the user changes the install directory
from the one that is default(it comes out as PipelineOptimizer 06.00.00)
to some other name, the file being copied using the CopyFile attribute
is still copied to the same directory under the programdata as the one
which is defaulted in the UI which is to C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00. What i want though is that if
the user changes the directory to say PipelineOptimizer 06.00.00 Test,
then the file should be copied to the C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00 Test but this does not happen.
Is there a way i can achieve the same. I tried using custom action to
set the property CopyDestination but was not able to do so. Please let
me know if there is a solution to this if possible with some sample code.
Also is there a way in which we can create 2 prompts to the user during
install. This would allow us to use the directory variable independent
of the path so that we can use this approach for the ProgramData subfolder .
i. Prompt 1: The install path. For example, the default path is
C:\Energy Solutions International\.
ii.Prompt 2: The install directory. For example, the default
directory is PipelineOptimizer 06.00.00.
and then use the value of the install directory somehow to copy the file
to right location. Is the above approach possible? Please help as it is
urgent for me.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fwd: How to have the shortcut name same as the installation directory
Thanks for the replies Phil and Jacob. I would look and try to find a
solution in the way that you have suggested.
But apart from this i have another requirement. Below is the code:
Property Id=CopyDestination Value=C:\ProgramData\Energy Solutions
International\PipelineOptimizer $(var.SvnVersion)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer $(var.SvnVersion)'
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
SetDirectory Id=EnergySolutions Value=C:\Energy Solutions
International/
Property Id=WIXUI_INSTALLDIR Value=TORT /
UIRef Id=WixUI_InstallDir /
While doing the installation if the user changes the install directory
from the one that is default(it comes out as PipelineOptimizer 06.00.00)
to some other name, the file being copied using the CopyFile attribute
is still copied to the same directory under the programdata as the one
which is defaulted in the UI which is to C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00. What i want though is that if
the user changes the directory to say PipelineOptimizer 06.00.00 Test,
then the file should be copied to the C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00 Test but this does not happen.
Is there a way i can achieve the same. I tried using custom action to
set the property CopyDestination but was not able to do so. Please let
me know if there is a solution to this if possible with some sample code.
Also is there a way in which we can create 2 prompts to the user during
install. This would allow us to use the directory variable independent
of the path so that we can use this approach for the ProgramData subfolder
i. Prompt 1: The install path. For example, the default path is
C:\Energy Solutions International\.
ii. Prompt 2: The install directory. For example, the default
directory is PipelineOptimizer 06.00.00.
and then use the value of the install directory somehow to copy the file
to right location. Is the above approach possible?
Regards,
Suvra Jyoti
On 10-03-2014 21:44, Hoover, Jacob wrote:
I believe you'd have to look into semi-custom actions. Idea is at runtime
injecting new records into the needed tables just early enough so that
standard windows installer functionality does the heavy lifting. Note, you
need to ensure this happens in all instances for
install/upgrade/repair/remove and without having a UI sequence. You're also
going to need to utilize the remember me property pattern to be able to
restore the values.
Is this doable, probably. Will it be easy, no.
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Monday, March 10, 2014 10:40 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Fwd: How to have the shortcut name same as the
installation directory
I don't believe this is possible using the standard shortcut creation
methods. The issue is that the underlying functionality is the Shortcut table
of the MSI file, and the name is not a variable that can be specified with a
property (it's not the Formatted type). That means you will need to invent
your own solution. You could use code to create the shortcuts, not something
anyone would recommend, or somehow modify the Shortcut table at install time,
---
Phil Wilson
On Mon, Mar 10, 2014 at 2:47 AM, Suvrajyoti Panda suvrajyo...@contata.co.in
wrote:
Adding on to this, i would like to use values supplied in the
dialogues of the installer. Also i would like to use one dialogue for
the installation path and the other for the installation directory.
Please let me know how i can achieve this.
Regards,
Suvra Jyoti
Original Message
Subject:How to have the shortcut name same as the installation
directory
Date: Mon, 10 Mar 2014 14:55:10 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I have the below directory structure:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ENERGYSOLUTIONS Name=$(var.rootFolder)
Directory Id='PFWLOCAL' Name=$(var.installFolder)
/Directory
/Directory
Directory Id=DesktopFolder Name=Desktop
Component Id=PFWLocalClientShortcutDesktopCmp
Guid={D24360C2-0D40-4CA9-BD9C-874D7DFEB5B1}
Shortcut Id=PFWLocalClientShortcutDesktop
Name=$(var.installFolder) Target=[PFWLOCAL]PFWLocalClient.exe
Description='Launch
[WiX-users] Creating directory under C:\Programdata same as what the user specified in the UI dialogue
Hi All,
I had appended this query in another topic, so reposting the same under
different heading.
I have this requirement in which i want to create directory under
C:\Programdata same as what the user specified in the UI dialogue .I am
trying to do that using CopyFile. Below is the code:
Property Id=CopyDestination Value=C:\ProgramData\Energy Solutions
International\PipelineOptimizer $(var.SvnVersion)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer $(var.SvnVersion)'
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
SetDirectory Id=EnergySolutions Value=C:\Energy Solutions
International/
Property Id=WIXUI_INSTALLDIR Value=TORT /
UIRef Id=WixUI_InstallDir /
While doing the installation if the user changes the install directory
from the one that is default(it comes out as PipelineOptimizer 06.00.00)
to some other name, the file being copied using the CopyFile attribute
is still copied to the same directory under the programdata as the one
which is defaulted in the UI which is to C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00. What i want though is that if
the user changes the directory to say PipelineOptimizer 06.00.00 Test,
then the file should be copied to the C:\ProgramData\Energy Solutions
International\PipelineOptimizer 06.00.00 Test but this does not happen.
Is there a way i can achieve the same. I tried using custom action to
set the property CopyDestination but was not able to do so. Please let
me know if there is a solution to this if possible with some sample code.
Also is there a way in which we can create 2 prompts to the user during
install. This would allow us to use the directory variable independent
of the path so that we can use this approach for the ProgramData subfolder .
i. Prompt 1: The install path. For example, the default path is
C:\Energy Solutions International\.
ii.Prompt 2: The install directory. For example, the default
directory is PipelineOptimizer 06.00.00.
and then use the value of the install directory somehow to copy the file
to right location. Is the above approach possible? Please help as it is
urgent for me.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Unable to install different versions of an application
Thanks for the confirmation Phil. I would try to find a solution to the
same.
On 08-03-2014 00:17, Phil Wilson wrote:
I don't believe that any of that is possible using anything in Windows
Installer or WiX, unless you build your own Burn functionality. It
seems to me that you'd need to inspect the system before installing
anything to see what is already installed, where it is installed, and
then choosing an install of one of the several MSI files I think you'd
need to cover those scenarios, one of which would upgrade and one or
more that wouldn't. You need some kind of pre-install program to do
that. The bottom line is that I think you'd have to invent the
functionality to achieve what you want, there's nothing I know of that
you can just pick up and use.
---
Phil Wilson
On Fri, Mar 7, 2014 at 2:28 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Yeah Phil i understood that. But if some has faced the below scenarios
to achieve, please let me know if it is possible to achieve these and how:
I am not able install different versions my application that i developed
with WIX. Below are my requirements
a.I want it to uninstall and reinstall automatically if the install is
in the same folder location say pipelineoptimizer 6.0.0. What this means
is that if it is the same build version i.e. 6.0.0 or simply say version
of the two products, we want it to overwrite. If it is a different
build version, we want it to install side by side. I put overwrite in
quotes because what it should actually do is uninstall and reinstall so
that it is a clean install.
b.I would also want it to install separately if it was 6.0.1 as well,
not just a change to the major number. Also, we don't want any manual
changes to the scripts when upgrading versions(say changing the upgrade
code).
C. If we are installing to same directory(say pipelineoptimizer 6.0.0),
it should uninstall/reinstall. If it is a different directory, it should
install side-by-side without uinstalling the previous one already
installed. Since the directories by default are ProductName
major.minor.revision, all 3 of those numbers have to be the same for
it to overwrite. However, if someone is intentionally doing a
side-by-side and changes the default directory, that should allow a
side-by-side install without uinstalling the previous one already installed.
Below is the code that i have:
Product Name='PipelineOptimizer $(var.SvnVersion)' Id='*'
UpgradeCode='{A73A66C4-CBC1-45DD-B6A3-85D6252AE592}'
Language='1033' Codepage='1252' Version='$(var.SvnVersionBuild)'
Manufacturer='$(var.ManufacturerName)'
Package Id='*' Keywords='Installer' Description=Tort Installer
1.0 Comments='Tort Installer' Platform='x64'
Manufacturer='$(var.ManufacturerName)'
InstallerVersion='300' Languages='1033' Compressed='yes'
SummaryCodepage='1252' /
MajorUpgrade AllowDowngrades='no' DowngradeErrorMessage=A later
version of [ProductName] is already installed.
Schedule=afterInstallInitialize /
Please let me know what changes i need to make.
Regards,
Suvra Jyoti
On 05-03-2014 23:53, Phil Wilson wrote:
Most of this is just the way that Windows Installer works, by design.
It's the ProductCode (that Id) that identifies the product, so you
cannot have the same product installed twice.
If your product version doesn't come out consistently, and is not what
was intended, then that sounds like a build problem to me. It's your
build process that should produce two separate versions, but
apparently it can't.
---
Phil Wilson
On Wed, Mar 5, 2014 at 4:16 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Hi All,
I am not able to install different versions of my application through
installer i have created side by side. It says that it is already
installed. We should be able to install 2 different builds.
Product Name='PipelineOptimizer Tort Engine $(var.SvnVersion)'
Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0'
UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057' Language='1033'
Codepage='1252' Version='$(var.SvnVersion)'
Manufacturer='$(var.ManufacturerName)'
Package Id='*' Keywords='Installer' Description=Tort Installer
1.0 Comments='Tort Installer' Platform='x64'
Manufacturer='$(var.ManufacturerName)'
InstallerVersion='300' Languages='1033' Compressed='yes'
SummaryCodepage='1252'/Package
In the above the Product version sometimes comes out as 06.00.3422 and
sometimes as 06.00.3424 .The first installer is able to install the
application(version 06.00.3422) but second one with version 06.00.3424
is not allowed to install.It says that it is already installed. I tried
changing the Product Id attribute to '*' and then it allows to install
the two versions side by side. But in this case even if the version
remains as 06.00.3422(since its is dynamic and i am fetching the
revision from svn) then we have two applications with the same same
[WiX-users] How to have the shortcut name same as the installation directory
Hi All,
I have the below directory structure:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ENERGYSOLUTIONS Name=$(var.rootFolder)
Directory Id='PFWLOCAL' Name=$(var.installFolder)
/Directory
/Directory
Directory Id=DesktopFolder Name=Desktop
Component Id=PFWLocalClientShortcutDesktopCmp
Guid={D24360C2-0D40-4CA9-BD9C-874D7DFEB5B1}
Shortcut Id=PFWLocalClientShortcutDesktop
Name=$(var.installFolder) Target=[PFWLOCAL]PFWLocalClient.exe
Description='Launch Pipeline Framework'
WorkingDirectory='PFWLOCAL' Icon='PFWLocalClientIcon.ico'
/Shortcut
RemoveFolder Id=DesktopFolder On=uninstall/
RegistryValue Root=HKCU
Key=Software\PipelineFramework Name=PFWLocalClientShortcutdesktop
Type=integer Value=1 KeyPath=yes/
/Component
/Directory
/Directory
And i am using the built in WIX UI as below:
Property Id=WIXUI_INSTALLDIR Value=PFWLOCAL /
In the desktop shortcut i am creating above, i want that the name
attribute of the shortcut be picked up same as the name of the directory
the user wants to install to, for instance he might change the default
directory, in that case the name of the shortcut should be same as the
directory user has supplied. Please let me know how we can achieve the same.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fwd: How to have the shortcut name same as the installation directory
Adding on to this, i would like to use values supplied in the dialogues
of the installer. Also i would like to use one dialogue for the
installation path and the other for the installation directory. Please
let me know how i can achieve this.
Regards,
Suvra Jyoti
Original Message
Subject:How to have the shortcut name same as the installation directory
Date: Mon, 10 Mar 2014 14:55:10 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I have the below directory structure:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ENERGYSOLUTIONS Name=$(var.rootFolder)
Directory Id='PFWLOCAL' Name=$(var.installFolder)
/Directory
/Directory
Directory Id=DesktopFolder Name=Desktop
Component Id=PFWLocalClientShortcutDesktopCmp
Guid={D24360C2-0D40-4CA9-BD9C-874D7DFEB5B1}
Shortcut Id=PFWLocalClientShortcutDesktop
Name=$(var.installFolder) Target=[PFWLOCAL]PFWLocalClient.exe
Description='Launch Pipeline Framework'
WorkingDirectory='PFWLOCAL' Icon='PFWLocalClientIcon.ico'
/Shortcut
RemoveFolder Id=DesktopFolder On=uninstall/
RegistryValue Root=HKCU
Key=Software\PipelineFramework Name=PFWLocalClientShortcutdesktop
Type=integer Value=1 KeyPath=yes/
/Component
/Directory
/Directory
And i am using the built in WIX UI as below:
Property Id=WIXUI_INSTALLDIR Value=PFWLOCAL /
In the desktop shortcut i am creating above, i want that the name
attribute of the shortcut be picked up same as the name of the directory
the user wants to install to, for instance he might change the default
directory, in that case the name of the shortcut should be same as the
directory user has supplied. Please let me know how we can achieve the same.
Regards,
Suvra Jyoti
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Unable to install different versions of an application
Yeah Phil i understood that. But if some has faced the below scenarios
to achieve, please let me know if it is possible to achieve these and how:
I am not able install different versions my application that i developed
with WIX. Below are my requirements
a.I want it to uninstall and reinstall automatically if the install is
in the same folder location say pipelineoptimizer 6.0.0. What this means
is that if it is the same build version i.e. 6.0.0 or simply say version
of the two products, we want it to overwrite. If it is a different
build version, we want it to install side by side. I put overwrite in
quotes because what it should actually do is uninstall and reinstall so
that it is a clean install.
b.I would also want it to install separately if it was 6.0.1 as well,
not just a change to the major number. Also, we don't want any manual
changes to the scripts when upgrading versions(say changing the upgrade
code).
C. If we are installing to same directory(say pipelineoptimizer 6.0.0),
it should uninstall/reinstall. If it is a different directory, it should
install side-by-side without uinstalling the previous one already
installed. Since the directories by default are ProductName
major.minor.revision, all 3 of those numbers have to be the same for
it to overwrite. However, if someone is intentionally doing a
side-by-side and changes the default directory, that should allow a
side-by-side install without uinstalling the previous one already installed.
Below is the code that i have:
Product Name='PipelineOptimizer $(var.SvnVersion)' Id='*'
UpgradeCode='{A73A66C4-CBC1-45DD-B6A3-85D6252AE592}'
Language='1033' Codepage='1252' Version='$(var.SvnVersionBuild)'
Manufacturer='$(var.ManufacturerName)'
Package Id='*' Keywords='Installer' Description=Tort Installer
1.0 Comments='Tort Installer' Platform='x64'
Manufacturer='$(var.ManufacturerName)'
InstallerVersion='300' Languages='1033' Compressed='yes'
SummaryCodepage='1252' /
MajorUpgrade AllowDowngrades='no' DowngradeErrorMessage=A later
version of [ProductName] is already installed.
Schedule=afterInstallInitialize /
Please let me know what changes i need to make.
Regards,
Suvra Jyoti
On 05-03-2014 23:53, Phil Wilson wrote:
Most of this is just the way that Windows Installer works, by design.
It's the ProductCode (that Id) that identifies the product, so you
cannot have the same product installed twice.
If your product version doesn't come out consistently, and is not what
was intended, then that sounds like a build problem to me. It's your
build process that should produce two separate versions, but
apparently it can't.
---
Phil Wilson
On Wed, Mar 5, 2014 at 4:16 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Hi All,
I am not able to install different versions of my application through
installer i have created side by side. It says that it is already
installed. We should be able to install 2 different builds.
Product Name='PipelineOptimizer Tort Engine $(var.SvnVersion)'
Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0'
UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057' Language='1033'
Codepage='1252' Version='$(var.SvnVersion)'
Manufacturer='$(var.ManufacturerName)'
Package Id='*' Keywords='Installer' Description=Tort Installer
1.0 Comments='Tort Installer' Platform='x64'
Manufacturer='$(var.ManufacturerName)'
InstallerVersion='300' Languages='1033' Compressed='yes'
SummaryCodepage='1252'/Package
In the above the Product version sometimes comes out as 06.00.3422 and
sometimes as 06.00.3424 .The first installer is able to install the
application(version 06.00.3422) but second one with version 06.00.3424
is not allowed to install.It says that it is already installed. I tried
changing the Product Id attribute to '*' and then it allows to install
the two versions side by side. But in this case even if the version
remains as 06.00.3422(since its is dynamic and i am fetching the
revision from svn) then we have two applications with the same same
version installed side by side. That's not something that should happen.
It should install the second version only if it is different from the
first.
If any one knows the workaround please provide your inputs on the same.
Regards
--
Subversion Kills Productivity. Get off Subversion Make the Move to
Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to pick the installation folder passed in the UI
Hi All, Could anybody please let me know how i can pick directory that the user chooses to install the application to to and use it in the Product name? Regards, Suvra Jyoti -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fwd: How to pick the installation folder passed in the UI
I am using the install dir as below: Property Id=WIXUI_INSTALLDIR Value=TORT / where TORT is the id of the directory where the installation is taking place. Original Message Subject:[WiX-users] How to pick the installation folder passed in the UI Date: Fri, 07 Mar 2014 11:07:15 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in Reply-To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Hi All, Could anybody please let me know how i can pick directory that the user chooses to install the application to to and use it in the Product name? Regards, Suvra Jyoti -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Unable to install different versions of an application
Hi All, I am not able to install different versions of my application through installer i have created side by side. It says that it is already installed. We should be able to install 2 different builds. Product Name='PipelineOptimizer Tort Engine $(var.SvnVersion)' Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0' UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057' Language='1033' Codepage='1252' Version='$(var.SvnVersion)' Manufacturer='$(var.ManufacturerName)' Package Id='*' Keywords='Installer' Description=Tort Installer 1.0 Comments='Tort Installer' Platform='x64' Manufacturer='$(var.ManufacturerName)' InstallerVersion='300' Languages='1033' Compressed='yes' SummaryCodepage='1252'/Package In the above the Product version sometimes comes out as 06.00.3422 and sometimes as 06.00.3424 .The first installer is able to install the application(version 06.00.3422) but second one with version 06.00.3424 is not allowed to install.It says that it is already installed. I tried changing the Product Id attribute to '*' and then it allows to install the two versions side by side. But in this case even if the version remains as 06.00.3422(since its is dynamic and i am fetching the revision from svn) then we have two applications with the same same version installed side by side. That's not something that should happen. It should install the second version only if it is different from the first. If any one knows the workaround please provide your inputs on the same. Regards -- Subversion Kills Productivity. Get off Subversion Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly
Hi Phil, After changing the type of the bootstrapper to output type .exe i am not facing the error below. Thanks for the pointer. But on the trying to install using the bootstrapper .exe created the .NEt framework does not get installed. It shows the message Microsoft .NET framework setup but then goes on to show the popup as below that shows the various usage options: Setup[switches] The other .msi package though does get installed. For all the packages i have set compressed=yes. I have changed the detect condition to as below from earlier for the .Net framework .exe package. Below is the same: PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full DisplayName=Microsoft .NET Framework 4.0 Compressed=yes Cache=yes PerMachine=yes Permanent=yes Protocol=netfx4 Vital=yes SourceFile=D:\Installables\.NET Framework 4\dotNetFx40_Full_x86_x64.exe InstallCommand=Setup /passive /norestart /ChainingPackage /q RepairCommand=/passive /norestart /repair /ChainingPackage /q UninstallCommand=/uninstall /passive /norestart /ChainingPackage /q DetectCondition=Netfx4FullVersion AND Netfx4x64FullVersion/ /PackageGroup In the log file also i can find that the Detectcondition evaluates to false. Attached is the same. But the .NET framework does start the installation. Could you please provide some help on this as this is urgent for me. Regards, Suvra Jyoti On 28-02-2014 19:42, Phill Hogland wrote: A project that creates a bootstrapper (and uses the Bundle element) should produce an EXE, and not an msi. An MSI does not have the appropriate 'entry point' which is what the error indicates. You might find it easier to use the built-in support for installing .Net 4.0. In my bootstrapper (exe) project I add: Bundle . BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost .. other files WixVariable Id=WixMbaPrereqPackageId Value=Netfx4ClientRedist / WixVariable Id=WixMbaPrereqLicenseUrl Value=NetfxLicense.rtf/ /BootstrapperApplicationRef /Bundle or look at: http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html you could also get a lot of information from src\ext\NetFxExtension\wixlib -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-NET-framework-4-0-install-does-not-work-properly-tp7593004p7593012.html Sent from the wix-users mailing list archive at Nabble.com. -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users [13B8:1304][2014-03-03T12:39:55]i001: Burn v3.8.1128.0, Windows v6.1 (Build 7601: Service Pack 1), path: D:\.net Framwork\PipelineOptimizerEngineInstallBootstrapper_06.00.00_3422.exe, cmdline: '' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\rakeshk\AppData\Local\Temp\OptimizerBootstrapper_20140303123956.log' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\.net Framwork\PipelineOptimizerEngineInstallBootstrapper_06.00.00_3422.exe' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleName' to value 'OptimizerBootstrapper' [13B8:1304][2014-03-03T12:39:56]i100: Detect begin, 2 packages [13B8:1304][2014-03-03T12:39:56]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full' [13B8:1304][2014-03-03T12:39:56]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full' [13B8:1304][2014-03-03T12:39:56]i052: Condition 'Netfx4FullVersion AND Netfx4x64FullVersion' evaluates to false. [13B8:1304][2014-03-03T12:39:56]i101: Detected package: Netfx4Full, state: Absent, cached: None [13B8:1304][2014-03-03T12:39:56]i101: Detected package: PipielineOptimizerEngineApp, state: Absent, cached: None [13B8:1304][2014-03-03T12:39:56]i199: Detect complete, result: 0x0 [13B8:0C7C][2014-03-03T12:39:58]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1 [13B8:1304][2014-03-03T12:39:58]i200: Plan begin, 2 packages, action: Install [13B8:1304][2014-03-03T12:39:58]w321: Skipping dependency registration on package with no dependency providers: Netfx4Full [13B8:1304][2014-03-03T12:39:58]i000:
[WiX-users] Fwd: Re: Bootstrapper for .NET framework 4.0 install does not work properly
Hi Phil, Also on examining the log a bit more carefully, i could see the below line applying execute package: Netfx4Full, action: Install, path: C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\dotNetFx40_Full_x86_x64.exe, arguments: 'C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\dotNetFx40_Full_x86_x64.exe /passive /norestart /ChainingPackage /q' Is there anything to be changed in the argument that are getting passed here. Regards, Suvra Jyoti Original Message Subject: Re: [WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly Date: Mon, 03 Mar 2014 14:06:30 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Hi Phil, After changing the type of the bootstrapper to output type .exe i am not facing the error below. Thanks for the pointer. But on the trying to install using the bootstrapper .exe created the .NEt framework does not get installed. It shows the message Microsoft .NET framework setup but then goes on to show the popup as below that shows the various usage options: Setup[switches] The other .msi package though does get installed. For all the packages i have set compressed=yes. I have changed the detect condition to as below from earlier for the .Net framework .exe package. Below is the same: PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full DisplayName=Microsoft .NET Framework 4.0 Compressed=yes Cache=yes PerMachine=yes Permanent=yes Protocol=netfx4 Vital=yes SourceFile=D:\Installables\.NET Framework 4\dotNetFx40_Full_x86_x64.exe InstallCommand=Setup /passive /norestart /ChainingPackage /q RepairCommand=/passive /norestart /repair /ChainingPackage /q UninstallCommand=/uninstall /passive /norestart /ChainingPackage /q DetectCondition=Netfx4FullVersion AND Netfx4x64FullVersion/ /PackageGroup In the log file also i can find that the Detectcondition evaluates to false. Attached is the same. But the .NET framework does start the installation. Could you please provide some help on this as this is urgent for me. Regards, Suvra Jyoti On 28-02-2014 19:42, Phill Hogland wrote: A project that creates a bootstrapper (and uses the Bundle element) should produce an EXE, and not an msi. An MSI does not have the appropriate 'entry point' which is what the error indicates. You might find it easier to use the built-in support for installing .Net 4.0. In my bootstrapper (exe) project I add: Bundle . BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost .. other files WixVariable Id=WixMbaPrereqPackageId Value=Netfx4ClientRedist / WixVariable Id=WixMbaPrereqLicenseUrl Value=NetfxLicense.rtf/ /BootstrapperApplicationRef /Bundle or look at: http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html you could also get a lot of information from src\ext\NetFxExtension\wixlib -- View this message in context:http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-NET-framework-4-0-install-does-not-work-properly-tp7593004p7593012.html Sent from the wix-users mailing list archive at Nabble.com. -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users [13B8:1304][2014-03-03T12:39:55]i001: Burn v3.8.1128.0, Windows v6.1 (Build 7601: Service Pack 1), path: D:\.net Framwork\PipelineOptimizerEngineInstallBootstrapper_06.00.00_3422.exe, cmdline: '' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\rakeshk\AppData\Local\Temp\OptimizerBootstrapper_20140303123956.log' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\.net Framwork\PipelineOptimizerEngineInstallBootstrapper_06.00.00_3422.exe' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleName' to value 'OptimizerBootstrapper' [13B8:1304][2014-03-03T12:39:56]i100: Detect begin, 2 packages [13B8:1304][2014-03-03T12:39:56]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full' [13B8:1304][2014-03-03T12:39:56]i000
Re: [WiX-users] Fwd: Re: Bootstrapper for .NET framework 4.0 install does not work properly
Hey Sally, And what else do i need to do to get it installed as in here do i need to provide the local path to the .net framework setup? On 03-03-2014 18:32, Pally Sandher wrote: Why aren't you simply using Chain PackageGroupRef Id=NetFx40Redist/ ... /Chain As per the manual at http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html ? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: 03 March 2014 09:45 To: General discussion about the WiX toolset. Subject: [WiX-users] Fwd: Re: Bootstrapper for .NET framework 4.0 install does not work properly Hi Phil, Also on examining the log a bit more carefully, i could see the below line applying execute package: Netfx4Full, action: Install, path: C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\dotNetFx40_Full_x86_x64.exe, arguments: 'C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\dotNetFx40_Full_x86_x64.exe /passive /norestart /ChainingPackage /q' Is there anything to be changed in the argument that are getting passed here. Regards, Suvra Jyoti Original Message Subject: Re: [WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly Date: Mon, 03 Mar 2014 14:06:30 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Hi Phil, After changing the type of the bootstrapper to output type .exe i am not facing the error below. Thanks for the pointer. But on the trying to install using the bootstrapper .exe created the .NEt framework does not get installed. It shows the message Microsoft .NET framework setup but then goes on to show the popup as below that shows the various usage options: Setup[switches] The other .msi package though does get installed. For all the packages i have set compressed=yes. I have changed the detect condition to as below from earlier for the .Net framework .exe package. Below is the same: PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full DisplayName=Microsoft .NET Framework 4.0 Compressed=yes Cache=yes PerMachine=yes Permanent=yes Protocol=netfx4 Vital=yes SourceFile=D:\Installables\.NET Framework 4\dotNetFx40_Full_x86_x64.exe InstallCommand=Setup /passive /norestart /ChainingPackage /q RepairCommand=/passive /norestart /repair /ChainingPackage /q UninstallCommand=/uninstall /passive /norestart /ChainingPackage /q DetectCondition=Netfx4FullVersion AND Netfx4x64FullVersion/ /PackageGroup In the log file also i can find that the Detectcondition evaluates to false. Attached is the same. But the .NET framework does start the installation. Could you please provide some help on this as this is urgent for me. Regards, Suvra Jyoti On 28-02-2014 19:42, Phill Hogland wrote: A project that creates a bootstrapper (and uses the Bundle element) should produce an EXE, and not an msi. An MSI does not have the appropriate 'entry point' which is what the error indicates. You might find it easier to use the built-in support for installing .Net 4.0. In my bootstrapper (exe) project I add: Bundle . BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost .. other files WixVariable Id=WixMbaPrereqPackageId Value=Netfx4ClientRedist / WixVariable Id=WixMbaPrereqLicenseUrl Value=NetfxLicense.rtf/ /BootstrapperApplicationRef /Bundle or look at: http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_ and_install_checks/install_dotnet.html you could also get a lot of information from src\ext\NetFxExtension\wixlib -- View this message in context:http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ Bootstrapper-for-NET-framework-4-0-install-does-not-work-properly-tp75 93004p7593012.html Sent from the wix-users mailing list archive at Nabble.com. -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network
[WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly
Hi All,
I want to create a bootstrapper for .NET framework 4.0 install as a
prerequisite for my application if it is not already present. Below is
how i designed my Bundle in which i am referencing my other WIX project:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle Name=OptimizerBootstrapper Version=1.0.0.0
Manufacturer=SuvraJyoti
UpgradeCode={1A9F7A91-A9F9-428E-ACD0-5D48621A0C83}
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
Chain
!-- .NET Framework --
PackageGroupRef Id=Netfx4Full/
!-- Install Application --
MsiPackage Id=PipielineOptimizerEngineApp
SourceFile=$(var.PipelineOptimizerEngineInstallPath)/
/Chain
/Bundle
Fragment
!-- Check for .NET 4.0 --
util:RegistrySearch Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework
Setup\NDP\v4\Full
Value=Version
Variable=Netfx4FullVersion /
util:RegistrySearch Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework
Setup\NDP\v4\Full
Value=Version
Variable=Netfx4x64FullVersion
Win64=yes /
!-- Install .NEt 4.0 --
PackageGroup Id=Netfx4Full
ExePackage Id=Netfx4Full
DisplayName=Microsoft .NET Framework 4.0
Compressed=no
Cache=yes
PerMachine=yes
Permanent=yes
Protocol=netfx4
Vital=yes
SourceFile=D:\Installables\.NET Framework
4\dotNetFx40_Full_x86_x64.exe
InstallCommand=/passive /norestart /ChainingPackage
RepairCommand=/passive /norestart /repair
/ChainingPackage /q
UninstallCommand=/uninstall /passive /norestart
/ChainingPackage /q
DetectCondition=Netfx4FullVersion AND (NOT
VersionNT64 OR Netfx4x64FullVersion) /
/PackageGroup
/Fragment
/Wix
I am getting the below warning as well:
/c:\CompletedBuilds\PLO\OptimizerBundle.wixobj : warning LGHT1109 :
Found mismatched entry point Bundle. Expected Product for specified
output package type.msi./
Also below are all the candle and light commands that i am using:
%WiXDir%\candle -ext WixUIExtension -out %outputPath%\ -I
.\TortInstaller\TortInstall.wxs %outputPath%\db.wxs
%outputPath%\data.wxs %outputPath%\engine.wxs %outputPath%\security.wxs
%outputPath%\gui.wxs -trace
%WiXDir%\light -ext WixUIExtension -out
%outputPath%\PipelineOptimizerEngineInstall_%VERSION%_%BUILD%.msi
%outputPath%\TortInstall.wixobj pause
::Referencing the BUNDLE here
%WiXDir%\candle -ext WixBalExtension -ext WixUtilExtension -out
%outputPath%\
-dPipelineOptimizerEngineInstallPath=%outputPath%\PipelineOptimizerEngineInstall_%VERSION%_%BUILD%.msi
-I .\TortInstaller\OptimizerBundle.wxs -trace
%WiXDir%\light -ext WixBalExtension -ext WixUtilExtension -out
%outputPath%\PipelineOptimizerEngineInstallBootstrapper_%VERSION%_%BUILD%.msi
%outputPath%\OptimizerBundle.wixobj
The PipelineOptimizerEngineInstallBootstrapper.msi that is created does
not seem to work. My system does have .NET framework 4.0 but that should
not mean that i should be getting the message as below on clicking the
Bootstrapper msi:
/The installation package could not be opened.Contact the application
vendor to verify that this is a valid Windows installer package/
Also i get to see that the dotNetFx40_Full_x86_x64.exe is produced in
the output path where the installers are ouput. Should this happen at all.
Please help me in getting these to work.
Regards,
Suvra Jyoti
--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fwd: Re: Not able to copy a file using CopyFile from installers install location to a target destination
Hey Guys, if you have any clue on the below issue please provide your
inputs on the same.
Regards,
Suvra Jyoti
Original Message
Subject:Re: [WiX-users] Not able to copy a file using CopyFile from
installers install location to a target destination
Date: Mon, 24 Feb 2014 12:46:56 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: wix-users@lists.sourceforge.net
Hi Phil,
Thanks for the suggestion. I have modified my wix source file as below
to use SourceDir in the Source attribute of File:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer 6.0.0'
Directory Id=CopiedFiles Name=Copied Files /
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={AD1478B2-D6DE-4855-9AFE-BFADDD63554F} Directory=SourceDir
File Id=FilePref Name=preferences.xml
Source=SourceDir\Energy Solutions International\PipelineOptimizer
6.0.0\gui\screens KeyPath=yes
CopyFile Id=Copy DestinationDirectory=CopiedFiles/
/File
/Component
SetDirectory Id=EnergySolutions Value=[WindowsVolume]Energy
Solutions International/
Feature Id='Complete' Title='Tort Installer' Description='Tort
Installer' Level='1'
ComponentGroupRef Id='gui'/ComponentGroupRef
ComponentRef Id=PreferencesFile /
/Feature
On executing the Light i am getting the below error:
C:\PLO\CruiseControl\TortInstaller\TortInstall.wxs(23) : error LGHT0103
: The system cannot find the file 'SourceDir\Energy Solutions
International\PipelineOpti
mizer 6.0.0\gui\screens'.
For the File Source attribute above, i have also used only SourceDir
value as well. The main issue is the resolution of the path to the file
that is inside componentgroupref Id 'gui' (subdirectory) that is created
by Heat.exe .As can be seen here the path to the preference.xml file is
in the gui\screens, created by the componentgroupref Id=gui directory
under which there is a screens directory which contains the file. The
structure thus formed on installation should be SourceDir\Energy
Solutions International\PipelineOptimizer 6.0.0\gui\screens\, which i am
not able to access and getting the path error.
The gui.wxs file created looks like below:
Fragment
DirectoryRef Id=TORT
Directory Id=dir9819615C78959640E45EA793F36FD3BB Name=gui
Component Id=cmp9DEB41E9A6D785D0FFB64755704DFDED
Guid={31302A86-80FD-4552-8037-B3CB54B12219}
File Id=filE2623651AE1B80ACDAB29B5020830498
KeyPath=yes Source=$(var.GuiPath)\mosquito.exe /
/Component
.
Fragment
ComponentGroup Id=gui
Please provide some help on the this, as this is urgent for me.
Regards,
Suvra Jyoti
On 21-02-2014 22:45, Phil Wilson wrote:
If you're doing an install time copyfile from the install location of
the MSI to a location on the system you need a copyfile that has
something like SourceDir as the source of the copy and EnergySolutions
as the destination.
---
Phil Wilson
On Fri, Feb 21, 2014 at 8:10 AM, John Cooperjocoo...@jackhenry.com wrote:
You're trying to copy to a privileged location. You need to either be
installing perMachine or you need to elevate and have an installing user
with Administrator privileges. An unprivileged user can't install or copy
to C:\Program Files ordinarily.
--
John Merryweather Cooper
Build Install Engineer - jXchange
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
From: Suvrajyoti Panda [suvrajyo...@contata.co.in]
Sent: Friday, February 21, 2014 4:07 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Not able to copy a file using CopyFile from installers
install location to a target destination
Hi All,
I have the requirement of creating an installer that on executing will
install to the location C:\Energy Solutions
International\PipelineOptimizer 6.0.0 the following 5 directories:
db,data,engine,security, gui. These five directories are being harvested
from a location using Heat. Below is the structure of the Wix source
file i have:
Property Id=CopyDestination
Value=$(var.copyRoot)\$(var.rootFolder)\$(var.installFolder)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer 6.0.0'
/Directory
/Directory
/Directory
SetDirectory Id=EnergySolutions Value=[WindowsVolume]Energy
Solutions International/
Feature Id='Complete' Title='Tort Installer' Description='Tort
Installer' Level='1'
ComponentGroupRef Id='db'/
ComponentGroupRef
Re: [WiX-users] Fwd: Re: Not able to copy a file using CopyFile from installers install location to a target destination
Hi Phil,
Below is how the issue was resolved:
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720} Directory=TARGETDIR
File Id='preferences'
Source='$(var.GuiPath)\screens\preferences.xml' KeyPath='yes'
CopyFile Id='Copy_Prefs'
DestinationProperty='CopyDestination' /
/File
/Component
Thanks for the inputs.
Regards,
Suva Jyoti
On 24-02-2014 21:55, Phil Wilson wrote:
You have a build error, that's why it's referring to the WiX source
file, just have the file in the right place for the build. It's not
building, so that means you haven't tested it yet.
Maybe you are confusing build time with install time? The copyfile
element at install time needs a source location and a destination
location. If you are copying from the same location as the installing
MSI file then you need the SourceDir property as the source location:
http://msdn.microsoft.com/en-us/library/aa371857(v=vs.85).aspx
---
Phil Wilson
On Mon, Feb 24, 2014 at 6:25 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in wrote:
Hey Guys, if you have any clue on the below issue please provide your
inputs on the same.
Regards,
Suvra Jyoti
Original Message
Subject:Re: [WiX-users] Not able to copy a file using CopyFile from
installers install location to a target destination
Date: Mon, 24 Feb 2014 12:46:56 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: wix-users@lists.sourceforge.net
Hi Phil,
Thanks for the suggestion. I have modified my wix source file as below
to use SourceDir in the Source attribute of File:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer 6.0.0'
Directory Id=CopiedFiles Name=Copied Files /
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={AD1478B2-D6DE-4855-9AFE-BFADDD63554F} Directory=SourceDir
File Id=FilePref Name=preferences.xml
Source=SourceDir\Energy Solutions International\PipelineOptimizer
6.0.0\gui\screens KeyPath=yes
CopyFile Id=Copy DestinationDirectory=CopiedFiles/
/File
/Component
SetDirectory Id=EnergySolutions Value=[WindowsVolume]Energy
Solutions International/
Feature Id='Complete' Title='Tort Installer' Description='Tort
Installer' Level='1'
ComponentGroupRef Id='gui'/ComponentGroupRef
ComponentRef Id=PreferencesFile /
/Feature
On executing the Light i am getting the below error:
C:\PLO\CruiseControl\TortInstaller\TortInstall.wxs(23) : error LGHT0103
: The system cannot find the file 'SourceDir\Energy Solutions
International\PipelineOpti
mizer 6.0.0\gui\screens'.
For the File Source attribute above, i have also used only SourceDir
value as well. The main issue is the resolution of the path to the file
that is inside componentgroupref Id 'gui' (subdirectory) that is created
by Heat.exe .As can be seen here the path to the preference.xml file is
in the gui\screens, created by the componentgroupref Id=gui directory
under which there is a screens directory which contains the file. The
structure thus formed on installation should be SourceDir\Energy
Solutions International\PipelineOptimizer 6.0.0\gui\screens\, which i am
not able to access and getting the path error.
The gui.wxs file created looks like below:
Fragment
DirectoryRef Id=TORT
Directory Id=dir9819615C78959640E45EA793F36FD3BB Name=gui
Component Id=cmp9DEB41E9A6D785D0FFB64755704DFDED
Guid={31302A86-80FD-4552-8037-B3CB54B12219}
File Id=filE2623651AE1B80ACDAB29B5020830498
KeyPath=yes Source=$(var.GuiPath)\mosquito.exe /
/Component
.
Fragment
ComponentGroup Id=gui
Please provide some help on the this, as this is urgent for me.
Regards,
Suvra Jyoti
On 21-02-2014 22:45, Phil Wilson wrote:
If you're doing an install time copyfile from the install location of
the MSI to a location on the system you need a copyfile that has
something like SourceDir as the source of the copy and EnergySolutions
as the destination.
---
Phil Wilson
On Fri, Feb 21, 2014 at 8:10 AM, John Cooperjocoo...@jackhenry.com wrote:
You're trying to copy to a privileged location. You need to either be
installing perMachine or you need to elevate and have an installing user
with Administrator privileges. An unprivileged user can't install or copy
to C:\Program Files ordinarily.
--
John Merryweather Cooper
Build Install Engineer - jXchange
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
From: Suvrajyoti Panda [suvrajyo
Re: [WiX-users] Not able to copy a file using CopyFile from installers install location to a target destination
Hi Phil,
Thanks for the suggestion. I have modified my wix source file as below
to use SourceDir in the Source attribute of File:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer 6.0.0'
Directory Id=CopiedFiles Name=Copied Files /
/Directory
/Directory
/Directory
Component Id=PreferencesFile
Guid={AD1478B2-D6DE-4855-9AFE-BFADDD63554F} Directory=SourceDir
File Id=FilePref Name=preferences.xml
Source=SourceDir\Energy Solutions International\PipelineOptimizer
6.0.0\gui\screens KeyPath=yes
CopyFile Id=Copy DestinationDirectory=CopiedFiles/
/File
/Component
SetDirectory Id=EnergySolutions Value=[WindowsVolume]Energy
Solutions International/
Feature Id='Complete' Title='Tort Installer' Description='Tort
Installer' Level='1'
ComponentGroupRef Id='gui'/ComponentGroupRef
ComponentRef Id=PreferencesFile /
/Feature
On executing the Light i am getting the below error:
C:\PLO\CruiseControl\TortInstaller\TortInstall.wxs(23) : error LGHT0103
: The system cannot find the file 'SourceDir\Energy Solutions
International\PipelineOpti
mizer 6.0.0\gui\screens'.
For the File Source attribute above, i have also used only SourceDir
value as well. The main issue is the resolution of the path to the file
that is inside componentgroupref Id 'gui' (subdirectory) that is created
by Heat.exe .As can be seen here the path to the preference.xml file is
in the gui\screens, created by the componentgroupref Id=gui directory
under which there is a screens directory which contains the file. The
structure thus formed on installation should be SourceDir\Energy
Solutions International\PipelineOptimizer 6.0.0\gui\screens\, which i am
not able to access and getting the path error.
The gui.wxs file created looks like below:
Fragment
DirectoryRef Id=TORT
Directory Id=dir9819615C78959640E45EA793F36FD3BB Name=gui
Component Id=cmp9DEB41E9A6D785D0FFB64755704DFDED
Guid={31302A86-80FD-4552-8037-B3CB54B12219}
File Id=filE2623651AE1B80ACDAB29B5020830498
KeyPath=yes Source=$(var.GuiPath)\mosquito.exe /
/Component
.
Fragment
ComponentGroup Id=gui
Please provide some help on the this, as this is urgent for me.
Regards,
Suvra Jyoti
On 21-02-2014 22:45, Phil Wilson wrote:
If you're doing an install time copyfile from the install location of
the MSI to a location on the system you need a copyfile that has
something like SourceDir as the source of the copy and EnergySolutions
as the destination.
---
Phil Wilson
On Fri, Feb 21, 2014 at 8:10 AM, John Cooper jocoo...@jackhenry.com wrote:
You're trying to copy to a privileged location. You need to either be
installing perMachine or you need to elevate and have an installing user
with Administrator privileges. An unprivileged user can't install or copy
to C:\Program Files ordinarily.
--
John Merryweather Cooper
Build Install Engineer - jXchange
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
From: Suvrajyoti Panda [suvrajyo...@contata.co.in]
Sent: Friday, February 21, 2014 4:07 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Not able to copy a file using CopyFile from installers
install location to a target destination
Hi All,
I have the requirement of creating an installer that on executing will
install to the location C:\Energy Solutions
International\PipelineOptimizer 6.0.0 the following 5 directories:
db,data,engine,security, gui. These five directories are being harvested
from a location using Heat. Below is the structure of the Wix source
file i have:
Property Id=CopyDestination
Value=$(var.copyRoot)\$(var.rootFolder)\$(var.installFolder)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer 6.0.0'
/Directory
/Directory
/Directory
SetDirectory Id=EnergySolutions Value=[WindowsVolume]Energy
Solutions International/
Feature Id='Complete' Title='Tort Installer' Description='Tort
Installer' Level='1'
ComponentGroupRef Id='db'/
ComponentGroupRef Id='data'/
ComponentGroupRef Id='engine'/
ComponentGroupRef Id='security'/
ComponentGroupRef Id='gui'/
ComponentRef Id=PreferencesFile /
/Feature
/Product
I want to copy a file called preferences.xml that will be found under
C:\Energy Solutions International\PipelineOptimizer 6.0.0\gui\screens on
installation to the c:\programdata\Energy Solutions
[WiX-users] Not able to copy a file using CopyFile from installers install location to a target destination
Hi All,
I have the requirement of creating an installer that on executing will
install to the location C:\Energy Solutions
International\PipelineOptimizer 6.0.0 the following 5 directories:
db,data,engine,security, gui. These five directories are being harvested
from a location using Heat. Below is the structure of the Wix source
file i have:
Property Id=CopyDestination
Value=$(var.copyRoot)\$(var.rootFolder)\$(var.installFolder)/
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutions' Name=Energy Solutions
International
Directory Id='TORT' Name='PipelineOptimizer 6.0.0'
/Directory
/Directory
/Directory
SetDirectory Id=EnergySolutions Value=[WindowsVolume]Energy
Solutions International/
Feature Id='Complete' Title='Tort Installer' Description='Tort
Installer' Level='1'
ComponentGroupRef Id='db'/
ComponentGroupRef Id='data'/
ComponentGroupRef Id='engine'/
ComponentGroupRef Id='security'/
ComponentGroupRef Id='gui'/
ComponentRef Id=PreferencesFile /
/Feature
/Product
I want to copy a file called preferences.xml that will be found under
C:\Energy Solutions International\PipelineOptimizer 6.0.0\gui\screens on
installation to the c:\programdata\Energy Solutions
International\PipelineOptimizer 6.0.0 as this file will be used by an
exe that would be present in the location of the installation at
C:\Energy Solutions International\PipelineOptimizer 6.0.0\gui
I am aware that the CopyFile would be used to do so but am not able to
use it properly. Please suggest some solution around the same.
I have tried something like the below:
DirectoryRef Id=TORT
Component Id=PreferencesFile
Guid={A4E1FFCE-1534-43BF-AA2B-CDFD39381720}
File Id=FilePref Source=gui\screens\preferencel.xml
KeyPath=yes
CopyFile Id=Copy DestinationProperty=CopyDestination/
/File
/Component
/DirectoryRef
But this does not work. Please provide some help on this as i am stuck
on this.
Regards,
Suvra Jyoti
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to select ASP.NET version
Hi Kiran,
I have used as below. Please see the app pool creation here.
DirectoryRef Id=MYWEBWEBSITE
!-- Configuring app pool --
Component Id=MyWebAppPoolCmp Guid= KeyPath=yes
iis:WebAppPool Id=MyWebAppPool Name=[WEB_APP_NAME]
ManagedRuntimeVersion=v4.0 ManagedPipelineMode=Integrated /
/Component
!-- Configure virtual dir --
Component Id=MyWebVirtualDirCmp
Guid={751DEB01-ECC1-48ff-869A-65BCEE9E0528} KeyPath=yes
iis:WebVirtualDir Id=MyWebVirtualDir
Alias=[VIRTUAL_DIR_VAL] Directory=MYWEBWEBSITE WebSite=DefaultWebSite
iis:WebDirProperties Id=MyWebVirtDirProperties
AnonymousAccess=yes BasicAuthentication=yes
WindowsAuthentication=yes /
iis:WebApplication Id=MyWebWebApplication
Name=[VIRTUAL_DIR_VAL] WebAppPool=MyWebAppPool /
/iis:WebVirtualDir
/Component
/DirectoryRef
Regards,
Suvra Jyoti
On 14-02-2014 16:17, Kiran Somisetty wrote:
Is there a way to provide the ASP.NET version while creating Web virtual
directory in wix installer. I have created a installer that creates a web
virtual directory, but I see the ASP.NET version is pointed to 2.0. I want
to set it to 4.0, rather than manually changing it.
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to select ASP.NET version
Just use the below for your app pool.
ManagedRuntimeVersion=v4.0
Could you please be more elaborate on the error you are facing.
On 14-02-2014 18:47, Kiran Somisetty wrote:
Thanks for the response.
I tried to implement like this, but I am getting a :1603 error during
installation, any clues on this.
On Fri, Feb 14, 2014 at 5:20 PM, Suvrajyoti Panda suvrajyo...@contata.co.in
wrote:
Hi Kiran,
I have used as below. Please see the app pool creation here.
DirectoryRef Id=MYWEBWEBSITE
!-- Configuring app pool --
Component Id=MyWebAppPoolCmp Guid= KeyPath=yes
iis:WebAppPool Id=MyWebAppPool Name=[WEB_APP_NAME]
ManagedRuntimeVersion=v4.0 ManagedPipelineMode=Integrated /
/Component
!-- Configure virtual dir --
Component Id=MyWebVirtualDirCmp
Guid={751DEB01-ECC1-48ff-869A-65BCEE9E0528} KeyPath=yes
iis:WebVirtualDir Id=MyWebVirtualDir
Alias=[VIRTUAL_DIR_VAL] Directory=MYWEBWEBSITE
WebSite=DefaultWebSite
iis:WebDirProperties Id=MyWebVirtDirProperties
AnonymousAccess=yes BasicAuthentication=yes
WindowsAuthentication=yes /
iis:WebApplication Id=MyWebWebApplication
Name=[VIRTUAL_DIR_VAL] WebAppPool=MyWebAppPool /
/iis:WebVirtualDir
/Component
/DirectoryRef
Regards,
Suvra Jyoti
On 14-02-2014 16:17, Kiran Somisetty wrote:
Is there a way to provide the ASP.NET version while creating Web virtual
directory in wix installer. I have created a installer that creates a web
virtual directory, but I see the ASP.NET version is pointed to 2.0. I
want
to set it to 4.0, rather than manually changing it.
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to select ASP.NET version
That is a property whose value i fetch from another include file
On 14-02-2014 19:19, Steven Ogilvie wrote:
Hi Suvrajyoti,
Curious, I don't use a iis.WebVirtualDir element but I do have
iis:WebDirProperties and iis:WebApplication
What is VIRTUAL_DIR_VAL ?
Thanks,
Steve
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: February-14-14 6:50 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] How to select ASP.NET version
Hi Kiran,
I have used as below. Please see the app pool creation here.
DirectoryRef Id=MYWEBWEBSITE
!-- Configuring app pool --
Component Id=MyWebAppPoolCmp Guid= KeyPath=yes
iis:WebAppPool Id=MyWebAppPool Name=[WEB_APP_NAME]
ManagedRuntimeVersion=v4.0 ManagedPipelineMode=Integrated /
/Component
!-- Configure virtual dir --
Component Id=MyWebVirtualDirCmp
Guid={751DEB01-ECC1-48ff-869A-65BCEE9E0528} KeyPath=yes
iis:WebVirtualDir Id=MyWebVirtualDir
Alias=[VIRTUAL_DIR_VAL] Directory=MYWEBWEBSITE WebSite=DefaultWebSite
iis:WebDirProperties Id=MyWebVirtDirProperties
AnonymousAccess=yes BasicAuthentication=yes
WindowsAuthentication=yes /
iis:WebApplication Id=MyWebWebApplication
Name=[VIRTUAL_DIR_VAL] WebAppPool=MyWebAppPool /
/iis:WebVirtualDir
/Component
/DirectoryRef
Regards,
Suvra Jyoti
On 14-02-2014 16:17, Kiran Somisetty wrote:
Is there a way to provide the ASP.NET version while creating Web
virtual directory in wix installer. I have created a installer that
creates a web virtual directory, but I see the ASP.NET version is
pointed to 2.0. I want to set it to 4.0, rather than manually changing it.
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Read a value from a text file and use it in WIX source file
Thanks Walter, that works for me :) On 12-02-2014 21:35, Walter Dexter wrote: Sorry I forgot about this. Here's what I'm doing. I'm sure someone more experienced will have a much better way, but this works for me. First, in my build.cmd file, set svt envrironment variable to the contents of the svnversion.txt file: set /p svt=svnversion.txt Then, pass it to candle on the command line: candle -dSvnVersion=%svt% main.wxs In main.wxs you can then use it as a variable. For example: Property Id=MCO_SVNVERSION Value=$(var.SvnVersion) / On Tue, Feb 11, 2014 at 9:34 AM, Suvrajyoti Panda suvrajyo...@contata.co.in wrote: Thanks Walter, that would be really helpful if you can give me an example. Regards, Suvra Jyoti On 11-02-2014 19:53, Walter Dexter wrote: It may not be the most elegant way, but I'm doing the same thing by passing the contents of the file (first line anyway) as a command line argument to the linker. I use a .cmd file to run the WiX ci mpile and link so its just a bit of batch file processing. If you need an example I can get it for you once I get to work. Let me know. On Feb 11, 2014 12:40 AM, Suvrajyoti Panda suvrajyo...@contata.co.in wrote: Hi All, I have a requirement wherein in i need to read a value from a text file located at D:\Project\ESI\Code\trunk\lastVersion.txt. This file contains a single line as below: 6.0.0 Build 3280 This 6.0.0 is basically the version . Now i want to read this value of version and use it in the name of the product in the WIX source file as below: Product *Name**='Tort Installer 1.0'* Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0' UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057' Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='$(var.ManufacturerName)' Instead of the 1.0 in the Name attribute i want to use the value of 6.0.0 that is there in the text file mentioned above. Please let me know how can i go about solving this issue. Regards, Suvra Jyoti -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Read a value from a text file and use it in WIX source file
Thanks Walter, that would be really helpful if you can give me an example. Regards, Suvra Jyoti On 11-02-2014 19:53, Walter Dexter wrote: It may not be the most elegant way, but I'm doing the same thing by passing the contents of the file (first line anyway) as a command line argument to the linker. I use a .cmd file to run the WiX ci mpile and link so its just a bit of batch file processing. If you need an example I can get it for you once I get to work. Let me know. On Feb 11, 2014 12:40 AM, Suvrajyoti Panda suvrajyo...@contata.co.in wrote: Hi All, I have a requirement wherein in i need to read a value from a text file located at D:\Project\ESI\Code\trunk\lastVersion.txt. This file contains a single line as below: 6.0.0 Build 3280 This 6.0.0 is basically the version . Now i want to read this value of version and use it in the name of the product in the WIX source file as below: Product *Name**='Tort Installer 1.0'* Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0' UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057' Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='$(var.ManufacturerName)' Instead of the 1.0 in the Name attribute i want to use the value of 6.0.0 that is there in the text file mentioned above. Please let me know how can i go about solving this issue. Regards, Suvra Jyoti -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Read a value from a text file and use it in WIX source file
Hi All, I have a requirement wherein in i need to read a value from a text file located at D:\Project\ESI\Code\trunk\lastVersion.txt. This file contains a single line as below: 6.0.0 Build 3280 This 6.0.0 is basically the version . Now i want to read this value of version and use it in the name of the product in the WIX source file as below: Product *Name**='Tort Installer 1.0'* Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0' UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057' Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='$(var.ManufacturerName)' Instead of the 1.0 in the Name attribute i want to use the value of 6.0.0 that is there in the text file mentioned above. Please let me know how can i go about solving this issue. Regards, Suvra Jyoti -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file
Not an issue Blair, i appreciate your concern. Attached is the bat
file(in text format) that i am using to create the msi installers. The
machine on which i run this will have the code checked out from svn(this
is my scenario) from where through heat i would harvest the file.
Ultimately i would call the bat file from the CCNET.Hope that helps.
Regards,
SuvraJyoti
On 21-01-2014 16:18, Blair Murri wrote:
And how do you intend to communicate that path into the MSI? And how will that
path relate to the source path of the files before they have been added to the
MSI when on other machines those files won’t exist yet?
I’m just trying to understand what your scenario is here to help guide you to a
working solution.
Blair
From: Suvrajyoti Panda
Sent: Monday, January 20, 2014 10:51 PM
To: General discussion for Windows Installer XML toolset.
I do intend, but for that scenario i am changing the path accordingly,
using %~d0\Installers path.
On 21-01-2014 11:07, Blair Murri wrote:
And you don’t intend on installing them on any other machine?
Blair
From: Suvrajyoti Panda
Sent: Monday, January 20, 2014 9:18 PM
To: General discussion for Windows Installer XML toolset.
Hi Blair,
I build them from the same machine at the same from another location.
Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
You only install MSIs on the same machine you build those MSIs from?
Blair
From: Suvrajyoti Panda
Sent: Wednesday, January 15, 2014 11:14 PM
To: General discussion for Windows Installer XML toolset.
Thanks David that works.
I have used as below:
Property Id=SIMULATORPATH
DirectorySearch Id=SimulatortDir Depth=6
Path=$(var.SimulatorSearchRoot) AssignToProperty=yes
FileSearch Id=StandaloneSimulator_exe
Name=StandaloneSimulator.exe/
/DirectorySearch
/Property
Adding to it, is there any way i can refer to the root directory of the
current directory where the wix file is. My wix file is in the location
D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
refer to the root directory D:\. I want to use this value in the path
attribute of DirectorySearch. If anyone has used the same please let me
know.
Regards,
SuvraJyoti
On 15-01-2014 20:53, David Watson wrote:
If you are not shipping the simulator and it is already on the target machine
you can use a directory/file search to search the hard disk for it then use the
resulting property to set the registry value.
See
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: 15 January 2014 11:51
To: General discussion about the WiX toolset.
Subject: [WiX-users] Fwd: Creating registry for an application installed
outside the current directory structure in WIX file
Hi All,
To add to the below issue, i understand that i could use a property that includes the
registry search. But issue here is that the application
StandaloneSimulator.exe is not something that has been installed on my
machine(i cannot find it under control panel). The
D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been checked out from
SVN.Please let me know in case there are any workarounds.
Original Message
Subject: Creating registry for an application installed outside the
current directory structure in WIX file
Date: Wed, 15 Jan 2014 12:44:55 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To:General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I am creating an wix installer. I want to create a registry entry whose path is
not under the directory structure created in the WIX file. Below is what i
intend to do:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='Scheduler' Name=Scheduler
Directory Id='PLTLPLOGAMERA' Name=Pipeline Scheduler Gamera
Component Id=x86RegEntGameraSimulatorPath
Guid={C769AC98-A3D0-4CB4-939F-F396B49D4E5F} Win64=no
RegistryValue Id=x86GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
*Value=D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin *Type=string /
/Component
Component Id=x64RegEntGameraSimulatorPath
Guid={0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C} Win64=yes
RegistryValue Id=x64GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
Value=*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin* Type=string /
/Component
/Directory
/Directory
/Directory
The *Value *in the above keys is the path where an application
standalonesimulator.exe is installed.Please suggest if there is anyway that i
do not have to hardcode this path. I know i
Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file
Hi Blair,
I build them from the same machine at the same from another location.
Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
You only install MSIs on the same machine you build those MSIs from?
Blair
From: Suvrajyoti Panda
Sent: Wednesday, January 15, 2014 11:14 PM
To: General discussion for Windows Installer XML toolset.
Thanks David that works.
I have used as below:
Property Id=SIMULATORPATH
DirectorySearch Id=SimulatortDir Depth=6
Path=$(var.SimulatorSearchRoot) AssignToProperty=yes
FileSearch Id=StandaloneSimulator_exe
Name=StandaloneSimulator.exe/
/DirectorySearch
/Property
Adding to it, is there any way i can refer to the root directory of the
current directory where the wix file is. My wix file is in the location
D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
refer to the root directory D:\. I want to use this value in the path
attribute of DirectorySearch. If anyone has used the same please let me
know.
Regards,
SuvraJyoti
On 15-01-2014 20:53, David Watson wrote:
If you are not shipping the simulator and it is already on the target
machine you can use a directory/file search to search the hard disk for it
then use the resulting property to set the registry value.
See
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: 15 January 2014 11:51
To: General discussion about the WiX toolset.
Subject: [WiX-users] Fwd: Creating registry for an application installed
outside the current directory structure in WIX file
Hi All,
To add to the below issue, i understand that i could use a property that
includes the registry search. But issue here is that the application
StandaloneSimulator.exe is not something that has been installed on my
machine(i cannot find it under control panel). The
D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been
checked out from SVN.Please let me know in case there are any workarounds.
Original Message
Subject: Creating registry for an application installed outside the
current directory structure in WIX file
Date: Wed, 15 Jan 2014 12:44:55 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To:General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I am creating an wix installer. I want to create a registry entry whose path
is not under the directory structure created in the WIX file. Below is what
i intend to do:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='Scheduler' Name=Scheduler
Directory Id='PLTLPLOGAMERA' Name=Pipeline Scheduler Gamera
Component Id=x86RegEntGameraSimulatorPath
Guid={C769AC98-A3D0-4CB4-939F-F396B49D4E5F} Win64=no
RegistryValue Id=x86GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
*Value=D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin *Type=string /
/Component
Component Id=x64RegEntGameraSimulatorPath
Guid={0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C} Win64=yes
RegistryValue Id=x64GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
Value=*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin* Type=string /
/Component
/Directory
/Directory
/Directory
The *Value *in the above keys is the path where an application
standalonesimulator.exe is installed.Please suggest if there is anyway
that i do not have to hardcode this path. I know i can use an include file
and fetch this path, but again that path will be harcoded in the include
file anyways.
Regards,
SuvraJyoti
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical
Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and
we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.
This message has been scanned for malware by Websense. www.websense.com
Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file
I do intend, but for that scenario i am changing the path accordingly,
using %~d0\Installers path.
On 21-01-2014 11:07, Blair Murri wrote:
And you don’t intend on installing them on any other machine?
Blair
From: Suvrajyoti Panda
Sent: Monday, January 20, 2014 9:18 PM
To: General discussion for Windows Installer XML toolset.
Hi Blair,
I build them from the same machine at the same from another location.
Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
You only install MSIs on the same machine you build those MSIs from?
Blair
From: Suvrajyoti Panda
Sent: Wednesday, January 15, 2014 11:14 PM
To: General discussion for Windows Installer XML toolset.
Thanks David that works.
I have used as below:
Property Id=SIMULATORPATH
DirectorySearch Id=SimulatortDir Depth=6
Path=$(var.SimulatorSearchRoot) AssignToProperty=yes
FileSearch Id=StandaloneSimulator_exe
Name=StandaloneSimulator.exe/
/DirectorySearch
/Property
Adding to it, is there any way i can refer to the root directory of the
current directory where the wix file is. My wix file is in the location
D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
refer to the root directory D:\. I want to use this value in the path
attribute of DirectorySearch. If anyone has used the same please let me
know.
Regards,
SuvraJyoti
On 15-01-2014 20:53, David Watson wrote:
If you are not shipping the simulator and it is already on the target
machine you can use a directory/file search to search the hard disk for it
then use the resulting property to set the registry value.
See
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: 15 January 2014 11:51
To: General discussion about the WiX toolset.
Subject: [WiX-users] Fwd: Creating registry for an application installed
outside the current directory structure in WIX file
Hi All,
To add to the below issue, i understand that i could use a property that
includes the registry search. But issue here is that the application
StandaloneSimulator.exe is not something that has been installed on my
machine(i cannot find it under control panel). The
D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been
checked out from SVN.Please let me know in case there are any workarounds.
Original Message
Subject: Creating registry for an application installed outside the
current directory structure in WIX file
Date: Wed, 15 Jan 2014 12:44:55 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To:General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not under the directory structure created in the WIX file. Below is
what i intend to do:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='Scheduler' Name=Scheduler
Directory Id='PLTLPLOGAMERA' Name=Pipeline Scheduler Gamera
Component Id=x86RegEntGameraSimulatorPath
Guid={C769AC98-A3D0-4CB4-939F-F396B49D4E5F} Win64=no
RegistryValue Id=x86GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
*Value=D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin *Type=string /
/Component
Component Id=x64RegEntGameraSimulatorPath
Guid={0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C} Win64=yes
RegistryValue Id=x64GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
Value=*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin* Type=string /
/Component
/Directory
/Directory
/Directory
The *Value *in the above keys is the path where an application
standalonesimulator.exe is installed.Please suggest if there is anyway
that i do not have to hardcode this path. I know i can use an include file
and fetch this path, but again that path will be harcoded in the include
file anyways.
Regards,
SuvraJyoti
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical
Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and
requires
Re: [WiX-users] (Please Ignore earlier mail)Creating an installer with spaces in the name with LIGHT command
Thanks Nicolas for the help. I will actually be putting it under D:\Installers\. On 15-01-2014 05:27, Nicolás Alvarez wrote: 2014/1/14 Suvrajyoti Pandasuvrajyo...@contata.co.in: Hi All, I want to create an installer in WIX that has spaces in its name something as shown below: light -out C:\Pipeline Scheduler Tortoise.msi C:\TortInstall.wixobj C:\db.wixobj How can i achieve the same? Please help on this if any body has encountered this before. Regards, SuvraJyoti Same way you handle that problem with any other command: add quotes around the path. light -out C:\Pipeline Scheduler Tortoise.msi C:\TortInstall.wixobj C:\db.wixobj Why are you putting those files directly in C:\ ? -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file
Hi All,
To add to the below issue, i understand that i could use a property that
includes the registry search. But issue here is that the application
StandaloneSimulator.exe is not something that has been installed on my
machine(i cannot find it under control panel). The
D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been
checked out from SVN.Please let me know in case there are any workarounds.
Original Message
Subject:Creating registry for an application installed outside the
current directory structure in WIX file
Date: Wed, 15 Jan 2014 12:44:55 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not under the directory structure created in the WIX file. Below
is what i intend to do:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='Scheduler' Name=Scheduler
Directory Id='PLTLPLOGAMERA' Name=Pipeline Scheduler Gamera
Component Id=x86RegEntGameraSimulatorPath
Guid={C769AC98-A3D0-4CB4-939F-F396B49D4E5F} Win64=no
RegistryValue Id=x86GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
*Value=D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin *Type=string /
/Component
Component Id=x64RegEntGameraSimulatorPath
Guid={0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C} Win64=yes
RegistryValue Id=x64GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
Value=*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin* Type=string /
/Component
/Directory
/Directory
/Directory
The *Value *in the above keys is the path where an application
standalonesimulator.exe is installed.Please suggest if there is anyway
that i do not have to hardcode this path. I know i can use an include
file and fetch this path, but again that path will be harcoded in the
include file anyways.
Regards,
SuvraJyoti
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file
Thanks David that works.
I have used as below:
Property Id=SIMULATORPATH
DirectorySearch Id=SimulatortDir Depth=6
Path=$(var.SimulatorSearchRoot) AssignToProperty=yes
FileSearch Id=StandaloneSimulator_exe
Name=StandaloneSimulator.exe/
/DirectorySearch
/Property
Adding to it, is there any way i can refer to the root directory of the
current directory where the wix file is. My wix file is in the location
D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
refer to the root directory D:\. I want to use this value in the path
attribute of DirectorySearch. If anyone has used the same please let me
know.
Regards,
SuvraJyoti
On 15-01-2014 20:53, David Watson wrote:
If you are not shipping the simulator and it is already on the target machine
you can use a directory/file search to search the hard disk for it then use
the resulting property to set the registry value.
See
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: 15 January 2014 11:51
To: General discussion about the WiX toolset.
Subject: [WiX-users] Fwd: Creating registry for an application installed
outside the current directory structure in WIX file
Hi All,
To add to the below issue, i understand that i could use a property that
includes the registry search. But issue here is that the application
StandaloneSimulator.exe is not something that has been installed on my
machine(i cannot find it under control panel). The
D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been
checked out from SVN.Please let me know in case there are any workarounds.
Original Message
Subject: Creating registry for an application installed outside the
current directory structure in WIX file
Date: Wed, 15 Jan 2014 12:44:55 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
Hi All,
I am creating an wix installer. I want to create a registry entry whose path
is not under the directory structure created in the WIX file. Below is what i
intend to do:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='Scheduler' Name=Scheduler
Directory Id='PLTLPLOGAMERA' Name=Pipeline Scheduler Gamera
Component Id=x86RegEntGameraSimulatorPath
Guid={C769AC98-A3D0-4CB4-939F-F396B49D4E5F} Win64=no
RegistryValue Id=x86GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
*Value=D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin *Type=string /
/Component
Component Id=x64RegEntGameraSimulatorPath
Guid={0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C} Win64=yes
RegistryValue Id=x64GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
Value=*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin* Type=string /
/Component
/Directory
/Directory
/Directory
The *Value *in the above keys is the path where an application
standalonesimulator.exe is installed.Please suggest if there is anyway that
i do not have to hardcode this path. I know i can use an include file and
fetch this path, but again that path will be harcoded in the include file
anyways.
Regards,
SuvraJyoti
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical
Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.
This message has been scanned for malware by Websense. www.websense.com
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140
[WiX-users] (Please Ignore earlier mail)Creating an installer with spaces in the name with LIGHT command
Hi All, I want to create an installer in WIX that has spaces in its name something as shown below: light -out C:\Pipeline Scheduler Tortoise.msi C:\TortInstall.wixobj C:\db.wixobj How can i achieve the same? Please help on this if any body has encountered this before. Regards, SuvraJyoti -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Creating registry for an application installed outside the current directory structure in WIX file
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not under the directory structure created in the WIX file. Below
is what i intend to do:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='Scheduler' Name=Scheduler
Directory Id='PLTLPLOGAMERA' Name=Pipeline Scheduler Gamera
Component Id=x86RegEntGameraSimulatorPath
Guid={C769AC98-A3D0-4CB4-939F-F396B49D4E5F} Win64=no
RegistryValue Id=x86GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
*Value=D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin *Type=string /
/Component
Component Id=x64RegEntGameraSimulatorPath
Guid={0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C} Win64=yes
RegistryValue Id=x64GameraSimulatorPathRegValue
Root=HKLM Key=SOFTWARE\[Manufacturer]
Name=$(var.standalonesimulatorRegName)
Value=*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin* Type=string /
/Component
/Directory
/Directory
/Directory
The *Value *in the above keys is the path where an application
standalonesimulator.exe is installed.Please suggest if there is anyway
that i do not have to hardcode this path. I know i can use an include
file and fetch this path, but again that path will be harcoded in the
include file anyways.
Regards,
SuvraJyoti
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Thanks for the clarification, that helps.
On 19-12-2013 14:55, Blair Murri wrote:
It’s like I wrote: Windows Installer will first try to move files it intends
on either replacing or deleting. If that succeeds, then the directory can
then be removed (but only if empty).
Files that cannot be deleted (whether moved or not) are marked for deletion
upon the next reboot if the transaction was successful. The mechanism for
removing files either doesn’t support directories or Windows Installer
doesn’t use it that way, and directories that couldn’t be removed before the
reboot are orphaned by Windows Installer. It’s been that way for years, I’ve
never seen a fix for it.
The only workarounds are to either only open files in such a way as to allow
them to be either moved or deleted while they are open (executable binaries
[DLL, EXE, etc.] are usually opened that way) or block uninstall from
succeeding while the file is still in use, or simply accept that an empty
directory, while not ideal, usually isn’t the end of the world. It takes
essentially no disk space, for instance, and doesn’t generally prevent
reinstallation from succeeding.
-Blair
From: Suvrajyoti Panda
Sent: Wednesday, December 18, 2013 8:40 PM
To: General discussion for Windows Installer XML toolset.
Yes it does exist after reboot as well.
On 18-12-2013 21:13, Hoover, Jacob wrote:
Does it exist after a reboot? I seem to remember windows installer being
smart enough to schedule some cleanup after reboot (if it couldn't do them
during uninstall).
-Original Message-
From: David Connet [mailto:d...@agilityrecordbook.com]
Sent: Wednesday, December 18, 2013 8:25 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstall by Installer not removing the path
created if that path is open on the system
There is no way (that I know of) to delete a directory where something has
an open handle on that. The only way is to make sure all programs have
stopped and no open programs have that as their current directory.
It's just like opening cmd.exe, cd'ing to a directory and trying to delete
that directory from explorer. Can't be done.
Dave
On 12/17/2013 10:50 PM, Suvrajyoti Panda wrote:
Hi Phil,
I modified the structure in my main WIX file as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=$(var.rootFolder)
Component Id=parentOfAll
Guid=22AD76A4-448E-41DB-85A0-A04E9774A466 KeyPath=yes
RemoveFolder Id= removeParent On=uninstall/
/Component
After installing i traversed to C:\Energy Solutions
International\PFWService\config\access then uninstalled the path
C:\Energy Solutions International\PFWService\ still exists, all the
files are deleted though.
On 17-12-2013 21:32, Phil Wilson wrote:
Why not just try a RemoveFolder and see if it solves the problem? It
is the most likely solution, as suggested before.
Phil Wilson
On Tue, Dec 17, 2013 at 5:16 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in
wrote:
I just thought i needed to reiterate the issue for better clarity:
Below is the directory structure in my source .wxs file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solution
International
Directory Id='PFWServiceFolder' Name=PFWService
Directory Id='CONFIG' Name=config
Component Id=x86RegEntPFWConfig
Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no
RegistryValue Id=x86PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
Component Id=x64RegEntPFWConfig
Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes
RegistryValue Id=x64PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
/Directory
/Directory
/Directory
/Directory
The heat harvests directories from a location D:\Configrelease which
has directories such as command_processors. The produces
config.wxs file that has below structure:
Fragment
DirectoryRef Id=CONFIG
Component Id=cmpC405575C36944E434C00DCE528FA79EA
Guid={0EDAF860-B5C3-4C93-BDD7-EB1947D94749}
File Id=fil62BA9BFC68F4D3C2DE913D9ABFEDC429
KeyPath=yes Source=$(var.ConfigPath)\PFWConfiguration.xml /
/Component
Directory Id=dirB9FCE785B12AD5549EC71DC5DC66ED48
Name=archives
/Directory
Directory Id=dirB8C0CFD798C8A57234B0C04A4E266B86
Name=command_processors
Component Id=cmpE03A5A54FF75ABF0FA6DA591BC4F3152
Guid={F2158D98-1DC2-4348-89FC-65A2115084B6
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Hey David,
Thanks for the confirmation.I just checked after reboot as well, but
that does not happen. Anyways thanks again.
Regards,
SuvraJyoti
On 18-12-2013 19:54, David Connet wrote:
There is no way (that I know of) to delete a directory where something
has an open handle on that. The only way is to make sure all programs
have stopped and no open programs have that as their current directory.
It's just like opening cmd.exe, cd'ing to a directory and trying to
delete that directory from explorer. Can't be done.
Dave
On 12/17/2013 10:50 PM, Suvrajyoti Panda wrote:
Hi Phil,
I modified the structure in my main WIX file as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=$(var.rootFolder)
Component Id=parentOfAll
Guid=22AD76A4-448E-41DB-85A0-A04E9774A466 KeyPath=yes
RemoveFolder Id= removeParent On=uninstall/
/Component
After installing i traversed to C:\Energy Solutions
International\PFWService\config\access then uninstalled the path
C:\Energy Solutions International\PFWService\ still exists, all the
files are deleted though.
On 17-12-2013 21:32, Phil Wilson wrote:
Why not just try a RemoveFolder and see if it solves the problem? It is
the most likely solution, as suggested before.
Phil Wilson
On Tue, Dec 17, 2013 at 5:16 AM, Suvrajyoti Panda suvrajyo...@contata.co.in
wrote:
I just thought i needed to reiterate the issue for better clarity:
Below is the directory structure in my source .wxs file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solution
International
Directory Id='PFWServiceFolder' Name=PFWService
Directory Id='CONFIG' Name=config
Component Id=x86RegEntPFWConfig
Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no
RegistryValue Id=x86PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
Component Id=x64RegEntPFWConfig
Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes
RegistryValue Id=x64PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
/Directory
/Directory
/Directory
/Directory
The heat harvests directories from a location D:\Configrelease which has
directories such as command_processors. The produces config.wxs file
that has below structure:
Fragment
DirectoryRef Id=CONFIG
Component Id=cmpC405575C36944E434C00DCE528FA79EA
Guid={0EDAF860-B5C3-4C93-BDD7-EB1947D94749}
File Id=fil62BA9BFC68F4D3C2DE913D9ABFEDC429
KeyPath=yes Source=$(var.ConfigPath)\PFWConfiguration.xml /
/Component
Directory Id=dirB9FCE785B12AD5549EC71DC5DC66ED48
Name=archives
/Directory
Directory Id=dirB8C0CFD798C8A57234B0C04A4E266B86
Name=command_processors
Component Id=cmpE03A5A54FF75ABF0FA6DA591BC4F3152
Guid={F2158D98-1DC2-4348-89FC-65A2115084B6} KeyPath=yes
CreateFolder /
/Component
After i run the installer, i browse to C:\Energy Solutions
International\PFWService\config\command_processors and keep this path
open, and then uninstall the directory structure that does not get
removed is C:\Energy Solutions International\PFWService.
Is it because of the CreateFolder in the config.wxs(as Wesley had
suggest) file that heat creates that i am facing this issue. If so what
is the way out. Hope i have explained the situation better this time,
apologies if i created any confusion.
Regards,
SuvraJyoti
On 17-12-2013 14:27, Suvrajyoti Panda wrote:
Hey Blair,
The scenario you have mentioned in the first para of your response is
exactly what is happening. So is there no way that we can handle the
folder removal on uninstall even if that path is open, or this is a
known issue?
Regards,
SuvraJyoti
On 17-12-2013 14:14, Blair Murri wrote:
If a file being removed can’t be moved, then it will be marked for
removal during reboot, and unfortunately the folder will then be left
behind (because only file delete records are placed into the reboot
sequence, not folders). After reboot there isn’t an installation left to
run to cleanup any further.
Most of the time, files still in use can be moved (even if they are
still loaded in other processes) and the folder is thus removed during the
installation transaction (before the reboot) and the moved file is then
removed as part of the reboot sequence.
-Blair
From: Suvrajyoti Panda
Sent: Monday, December 16, 2013 8:57 PM
To: General discussion for Windows Installer XML toolset.
No Wesley, I have not used any create folder over here
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Yes it does exist after reboot as well.
On 18-12-2013 21:13, Hoover, Jacob wrote:
Does it exist after a reboot? I seem to remember windows installer being
smart enough to schedule some cleanup after reboot (if it couldn't do them
during uninstall).
-Original Message-
From: David Connet [mailto:d...@agilityrecordbook.com]
Sent: Wednesday, December 18, 2013 8:25 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstall by Installer not removing the path created
if that path is open on the system
There is no way (that I know of) to delete a directory where something has an
open handle on that. The only way is to make sure all programs have stopped
and no open programs have that as their current directory.
It's just like opening cmd.exe, cd'ing to a directory and trying to delete
that directory from explorer. Can't be done.
Dave
On 12/17/2013 10:50 PM, Suvrajyoti Panda wrote:
Hi Phil,
I modified the structure in my main WIX file as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=$(var.rootFolder)
Component Id=parentOfAll
Guid=22AD76A4-448E-41DB-85A0-A04E9774A466 KeyPath=yes
RemoveFolder Id= removeParent On=uninstall/
/Component
After installing i traversed to C:\Energy Solutions
International\PFWService\config\access then uninstalled the path
C:\Energy Solutions International\PFWService\ still exists, all the
files are deleted though.
On 17-12-2013 21:32, Phil Wilson wrote:
Why not just try a RemoveFolder and see if it solves the problem? It
is the most likely solution, as suggested before.
Phil Wilson
On Tue, Dec 17, 2013 at 5:16 AM, Suvrajyoti Panda
suvrajyo...@contata.co.in
wrote:
I just thought i needed to reiterate the issue for better clarity:
Below is the directory structure in my source .wxs file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solution
International
Directory Id='PFWServiceFolder' Name=PFWService
Directory Id='CONFIG' Name=config
Component Id=x86RegEntPFWConfig
Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no
RegistryValue Id=x86PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
Component Id=x64RegEntPFWConfig
Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes
RegistryValue Id=x64PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
/Directory
/Directory
/Directory
/Directory
The heat harvests directories from a location D:\Configrelease which
has directories such as command_processors. The produces
config.wxs file that has below structure:
Fragment
DirectoryRef Id=CONFIG
Component Id=cmpC405575C36944E434C00DCE528FA79EA
Guid={0EDAF860-B5C3-4C93-BDD7-EB1947D94749}
File Id=fil62BA9BFC68F4D3C2DE913D9ABFEDC429
KeyPath=yes Source=$(var.ConfigPath)\PFWConfiguration.xml /
/Component
Directory Id=dirB9FCE785B12AD5549EC71DC5DC66ED48
Name=archives
/Directory
Directory Id=dirB8C0CFD798C8A57234B0C04A4E266B86
Name=command_processors
Component Id=cmpE03A5A54FF75ABF0FA6DA591BC4F3152
Guid={F2158D98-1DC2-4348-89FC-65A2115084B6} KeyPath=yes
CreateFolder /
/Component
After i run the installer, i browse to C:\Energy Solutions
International\PFWService\config\command_processors and keep this
path open, and then uninstall the directory structure that does not
get removed is C:\Energy Solutions International\PFWService.
Is it because of the CreateFolder in the config.wxs(as Wesley had
suggest) file that heat creates that i am facing this issue. If so
what is the way out. Hope i have explained the situation better this
time, apologies if i created any confusion.
Regards,
SuvraJyoti
On 17-12-2013 14:27, Suvrajyoti Panda wrote:
Hey Blair,
The scenario you have mentioned in the first para of your response
is exactly what is happening. So is there no way that we can handle
the folder removal on uninstall even if that path is open, or this
is a known issue?
Regards,
SuvraJyoti
On 17-12-2013 14:14, Blair Murri wrote:
If a file being removed can't be moved, then it will be marked for
removal during reboot, and unfortunately the folder will then be
left behind (because only file delete records are placed into the
reboot sequence, not folders). After reboot there isn't an
installation left to run to cleanup any further.
Most of the time, files still in use can be moved (even if they
are
still loaded in other
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Hey Blair, The scenario you have mentioned in the first para of your response is exactly what is happening. So is there no way that we can handle the folder removal on uninstall even if that path is open, or this is a known issue? Regards, SuvraJyoti On 17-12-2013 14:14, Blair Murri wrote: If a file being removed can’t be moved, then it will be marked for removal during reboot, and unfortunately the folder will then be left behind (because only file delete records are placed into the reboot sequence, not folders). After reboot there isn’t an installation left to run to cleanup any further. Most of the time, files still in use can be moved (even if they are still loaded in other processes) and the folder is thus removed during the installation transaction (before the reboot) and the moved file is then removed as part of the reboot sequence. -Blair From: Suvrajyoti Panda Sent: Monday, December 16, 2013 8:57 PM To: General discussion for Windows Installer XML toolset. No Wesley, I have not used any create folder over here. Regards, SuvraJyoti On 16-12-2013 20:03, Wesley Manning wrote: Did you use CreateFolder to create this directory? If so I think you need to use RemoveFolder to remove the folder. Not sure about that though. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-16-13 12:37 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hey Wesley, checked it on a reboot, that does not work. The structure is still there. Any others suggestions guys? Regards, SuvraJyoti On 13-12-2013 20:13, Wesley Manning wrote: It might be removed on a reboot. If you had folder open, then windows installer can't uninstall it. But I think it marks it for removal. I know for sure files have this behaviour but I'm not sure about folders. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-13-13 1:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hi All, I just saw this behaviour. My installer creates the following :C:\Energy Solutions International\PFWService\config, if this path is open and i run the uninstall from control panel, then the path remains(C:\Energy Solutions International\PFWService\config) although files under it is removed. Is it expected behavior or incorrect. If incorrect what is the workaround for the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
I just thought i needed to reiterate the issue for better clarity:
Below is the directory structure in my source .wxs file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solution
International
Directory Id='PFWServiceFolder' Name=PFWService
Directory Id='CONFIG' Name=config
Component Id=x86RegEntPFWConfig
Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no
RegistryValue Id=x86PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
Component Id=x64RegEntPFWConfig
Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes
RegistryValue Id=x64PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
/Directory
/Directory
/Directory
/Directory
The heat harvests directories from a location D:\Configrelease which has
directories such as command_processors. The produces config.wxs file
that has below structure:
Fragment
DirectoryRef Id=CONFIG
Component Id=cmpC405575C36944E434C00DCE528FA79EA
Guid={0EDAF860-B5C3-4C93-BDD7-EB1947D94749}
File Id=fil62BA9BFC68F4D3C2DE913D9ABFEDC429
KeyPath=yes Source=$(var.ConfigPath)\PFWConfiguration.xml /
/Component
Directory Id=dirB9FCE785B12AD5549EC71DC5DC66ED48
Name=archives
/Directory
Directory Id=dirB8C0CFD798C8A57234B0C04A4E266B86
Name=command_processors
Component Id=cmpE03A5A54FF75ABF0FA6DA591BC4F3152
Guid={F2158D98-1DC2-4348-89FC-65A2115084B6} KeyPath=yes
CreateFolder /
/Component
After i run the installer, i browse to C:\Energy Solutions
International\PFWService\config\command_processors and keep this path
open, and then uninstall the directory structure that does not get
removed is C:\Energy Solutions International\PFWService.
Is it because of the CreateFolder in the config.wxs(as Wesley had
suggest) file that heat creates that i am facing this issue. If so what
is the way out. Hope i have explained the situation better this time,
apologies if i created any confusion.
Regards,
SuvraJyoti
On 17-12-2013 14:27, Suvrajyoti Panda wrote:
Hey Blair,
The scenario you have mentioned in the first para of your response is
exactly what is happening. So is there no way that we can handle the
folder removal on uninstall even if that path is open, or this is a
known issue?
Regards,
SuvraJyoti
On 17-12-2013 14:14, Blair Murri wrote:
If a file being removed can’t be moved, then it will be marked for removal
during reboot, and unfortunately the folder will then be left behind
(because only file delete records are placed into the reboot sequence, not
folders). After reboot there isn’t an installation left to run to cleanup
any further.
Most of the time, files still in use can be moved (even if they are still
loaded in other processes) and the folder is thus removed during the
installation transaction (before the reboot) and the moved file is then
removed as part of the reboot sequence.
-Blair
From: Suvrajyoti Panda
Sent: Monday, December 16, 2013 8:57 PM
To: General discussion for Windows Installer XML toolset.
No Wesley, I have not used any create folder over here.
Regards,
SuvraJyoti
On 16-12-2013 20:03, Wesley Manning wrote:
Did you use CreateFolder to create this directory? If so I think you need
to use RemoveFolder to remove the folder. Not sure about that though.
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: December-16-13 12:37 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstall by Installer not removing the path
created if that path is open on the system
Hey Wesley,
checked it on a reboot, that does not work. The structure is still there.
Any others suggestions guys?
Regards,
SuvraJyoti
On 13-12-2013 20:13, Wesley Manning wrote:
It might be removed on a reboot. If you had folder open, then windows
installer can't uninstall it. But I think it marks it for removal. I
know for sure files have this behaviour but I'm not sure about folders.
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: December-13-13 1:48 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Uninstall by Installer not removing the path
created if that path is open on the system
Hi All,
I just saw this behaviour. My installer creates the following :C:\Energy
Solutions International\PFWService\config, if this path is open and i run
the uninstall from control panel, then the path remains(C:\Energy
Solutions International\PFWService\config) although files under it is
removed. Is it expected
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Hi Phil,
I modified the structure in my main WIX file as below:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=$(var.rootFolder)
Component Id=parentOfAll
Guid=22AD76A4-448E-41DB-85A0-A04E9774A466 KeyPath=yes
RemoveFolder Id= removeParent On=uninstall/
/Component
After installing i traversed to C:\Energy Solutions
International\PFWService\config\access then uninstalled the path
C:\Energy Solutions International\PFWService\ still exists, all the
files are deleted though.
On 17-12-2013 21:32, Phil Wilson wrote:
Why not just try a RemoveFolder and see if it solves the problem? It is
the most likely solution, as suggested before.
Phil Wilson
On Tue, Dec 17, 2013 at 5:16 AM, Suvrajyoti Panda suvrajyo...@contata.co.in
wrote:
I just thought i needed to reiterate the issue for better clarity:
Below is the directory structure in my source .wxs file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solution
International
Directory Id='PFWServiceFolder' Name=PFWService
Directory Id='CONFIG' Name=config
Component Id=x86RegEntPFWConfig
Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no
RegistryValue Id=x86PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
Component Id=x64RegEntPFWConfig
Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes
RegistryValue Id=x64PFWConfigRegValue Root=HKLM
Key=SOFTWARE\[Manufacturer] Name=ConfigPath Value=[CONFIG]
Type=string /
/Component
/Directory
/Directory
/Directory
/Directory
The heat harvests directories from a location D:\Configrelease which has
directories such as command_processors. The produces config.wxs file
that has below structure:
Fragment
DirectoryRef Id=CONFIG
Component Id=cmpC405575C36944E434C00DCE528FA79EA
Guid={0EDAF860-B5C3-4C93-BDD7-EB1947D94749}
File Id=fil62BA9BFC68F4D3C2DE913D9ABFEDC429
KeyPath=yes Source=$(var.ConfigPath)\PFWConfiguration.xml /
/Component
Directory Id=dirB9FCE785B12AD5549EC71DC5DC66ED48
Name=archives
/Directory
Directory Id=dirB8C0CFD798C8A57234B0C04A4E266B86
Name=command_processors
Component Id=cmpE03A5A54FF75ABF0FA6DA591BC4F3152
Guid={F2158D98-1DC2-4348-89FC-65A2115084B6} KeyPath=yes
CreateFolder /
/Component
After i run the installer, i browse to C:\Energy Solutions
International\PFWService\config\command_processors and keep this path
open, and then uninstall the directory structure that does not get
removed is C:\Energy Solutions International\PFWService.
Is it because of the CreateFolder in the config.wxs(as Wesley had
suggest) file that heat creates that i am facing this issue. If so what
is the way out. Hope i have explained the situation better this time,
apologies if i created any confusion.
Regards,
SuvraJyoti
On 17-12-2013 14:27, Suvrajyoti Panda wrote:
Hey Blair,
The scenario you have mentioned in the first para of your response is
exactly what is happening. So is there no way that we can handle the
folder removal on uninstall even if that path is open, or this is a
known issue?
Regards,
SuvraJyoti
On 17-12-2013 14:14, Blair Murri wrote:
If a file being removed can’t be moved, then it will be marked for
removal during reboot, and unfortunately the folder will then be left
behind (because only file delete records are placed into the reboot
sequence, not folders). After reboot there isn’t an installation left to
run to cleanup any further.
Most of the time, files still in use can be moved (even if they are
still loaded in other processes) and the folder is thus removed during the
installation transaction (before the reboot) and the moved file is then
removed as part of the reboot sequence.
-Blair
From: Suvrajyoti Panda
Sent: Monday, December 16, 2013 8:57 PM
To: General discussion for Windows Installer XML toolset.
No Wesley, I have not used any create folder over here.
Regards,
SuvraJyoti
On 16-12-2013 20:03, Wesley Manning wrote:
Did you use CreateFolder to create this directory? If so I think you
need to use RemoveFolder to remove the folder. Not sure about that though.
-Original Message-
From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
Sent: December-16-13 12:37 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Uninstall by Installer not removing the path
created if that path is open on the system
Hey Wesley,
checked it on a reboot, that does not work. The structure is still
there. Any others suggestions guys?
Regards,
SuvraJyoti
On 13-12-2013
[WiX-users] heat.exe : warning HEAT5151
Hi All, I am creating a WIX installer. In the heat part i am getting the below warning: heat.exe : warning HEAT5151 : Could not harvest data from a file that was expected to be an assembly: D:\configRelease\command_processors\bpolympic\OraclePull.dll. If this file is not an assembly you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Could not load file or assembly 'PFWCommandProcessor, Version=5.3.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. The heat is harvesting D:\configRelease\command_processors\bpolympic\OraclePull.dll . The installer gets created and on running the installer the path created is C:\Energy Solutions International\PFWService\config\command_processors\bpolympic (this is what i have defined) and the file is also there i.e the OraclePull.dll(of the same size as source). The file C:\Energy Solutions International\PFWService\config\command_processors\ExampleCommandProcessor\PFW\PFWCommandProcessor.dll is also there. The version though shown for this file is 1.0.0.0 Do i need to worry about this warning? If so please let me know how i can handle the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
No Wesley, I have not used any create folder over here. Regards, SuvraJyoti On 16-12-2013 20:03, Wesley Manning wrote: Did you use CreateFolder to create this directory? If so I think you need to use RemoveFolder to remove the folder. Not sure about that though. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-16-13 12:37 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hey Wesley, checked it on a reboot, that does not work. The structure is still there. Any others suggestions guys? Regards, SuvraJyoti On 13-12-2013 20:13, Wesley Manning wrote: It might be removed on a reboot. If you had folder open, then windows installer can't uninstall it. But I think it marks it for removal. I know for sure files have this behaviour but I'm not sure about folders. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-13-13 1:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hi All, I just saw this behaviour. My installer creates the following :C:\Energy Solutions International\PFWService\config, if this path is open and i run the uninstall from control panel, then the path remains(C:\Energy Solutions International\PFWService\config) although files under it is removed. Is it expected behavior or incorrect. If incorrect what is the workaround for the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users mNo -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe : warning HEAT5151
Hi John, Thanks for the reply, could you please let me know what are the different ways to increment the assembly file version? Regards, SuvraJyoti On 16-12-2013 19:47, John Cooper wrote: Not all version numbers are created equal. 5.3.1.0 probably reflects the AssemblyVersion which impacts the strong naming. 1.0.0.0 reflects the AssemblyFileVersion. You should be concerned that your build process is not incrementing the AssemblyFileVersion. This is the version that the installer uses to determine whether to overwrite an existing assembly. There are a number of ways to get the AssemblyFileVersion to increment. But if you don't choose one, your patching and upgrading is going to be unreliable to say the least. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: Monday, December 16, 2013 4:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] heat.exe : warning HEAT5151 Hi All, I am creating a WIX installer. In the heat part i am getting the below warning: heat.exe : warning HEAT5151 : Could not harvest data from a file that was expected to be an assembly: D:\configRelease\command_processors\bpolympic\OraclePull.dll. If this file is not an assembly you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Could not load file or assembly 'PFWCommandProcessor, Version=5.3.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. The heat is harvesting D:\configRelease\command_processors\bpolympic\OraclePull.dll . The installer gets created and on running the installer the path created is C:\Energy Solutions International\PFWService\config\command_processors\bpolympic (this is what i have defined) and the file is also there i.e the OraclePull.dll(of the same size as source). The file C:\Energy Solutions International\PFWService\config\command_processors\ExampleCommandProcessor\PFW\PFWCommandProcessor.dll is also there. The version though shown for this file is 1.0.0.0 Do i need to worry about this warning? If so please let me know how i can handle the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating Registry Key
Hi Nicolas, I just got it reviewed and as of now it does not cause much of a bother to me at this point of time. Thanks for the reply. Thanks, SuvraJyoti On 16-12-2013 21:12, Nicolás Alvarez wrote: Does he extra slash cause you actual trouble? Does it bother you enough to justify a custom action? El lunes, 16 de diciembre de 2013, Suvrajyoti Panda escribió: Thanks for the solution Blair. Would try this. Regards, SuvraJyoti On 15-12-2013 16:24, Blair Murri wrote: Only with a custom action -Blair From: Suvrajyoti Panda Sent: Thursday, December 12, 2013 9:51 PM To: General discussion for Windows Installer XML toolset. Hi All, May be this is a trivial question to ask, but below is what i want to achieve: I am creating registry entries as below in WIX source file: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutionsConfig' Name=Energy Solutions International Directory Id='PFWServiceFolder' Name='PFWService' Directory Id='CONFIG' Name='config' Component Id=x86RegEntPFWConfig Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no RegistryValue Id=x86PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component Component Id=x64RegEntPFWConfig Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes RegistryValue Id=x64PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component /Directory /Directory /Directory /Directory It creates the registry entry as : Is it possible that the slash after config in the above path can be done away with and the key value is C:\Energy Solutions International\PFWService\config instead, or the one created is the correct one. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-uhttps://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating Registry Key
Thanks for the solution Blair. Would try this. Regards, SuvraJyoti On 15-12-2013 16:24, Blair Murri wrote: Only with a custom action -Blair From: Suvrajyoti Panda Sent: Thursday, December 12, 2013 9:51 PM To: General discussion for Windows Installer XML toolset. Hi All, May be this is a trivial question to ask, but below is what i want to achieve: I am creating registry entries as below in WIX source file: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutionsConfig' Name=Energy Solutions International Directory Id='PFWServiceFolder' Name='PFWService' Directory Id='CONFIG' Name='config' Component Id=x86RegEntPFWConfig Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no RegistryValue Id=x86PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component Component Id=x64RegEntPFWConfig Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes RegistryValue Id=x64PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component /Directory /Directory /Directory /Directory It creates the registry entry as : Is it possible that the slash after config in the above path can be done away with and the key value is C:\Energy Solutions International\PFWService\config instead, or the one created is the correct one. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Hey Wesley, checked it on a reboot, that does not work. The structure is still there. Any others suggestions guys? Regards, SuvraJyoti On 13-12-2013 20:13, Wesley Manning wrote: It might be removed on a reboot. If you had folder open, then windows installer can't uninstall it. But I think it marks it for removal. I know for sure files have this behaviour but I'm not sure about folders. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-13-13 1:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hi All, I just saw this behaviour. My installer creates the following :C:\Energy Solutions International\PFWService\config, if this path is open and i run the uninstall from control panel, then the path remains(C:\Energy Solutions International\PFWService\config) although files under it is removed. Is it expected behavior or incorrect. If incorrect what is the workaround for the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registry key created
Hi All, I am creating registry entries as below in WIX source file: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutionsConfig' Name=Energy Solutions International Directory Id='PFWServiceFolder' Name='PFWService' Directory Id='CONFIG' Name='config' Component Id=x86RegEntPFWConfig Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no RegistryValue Id=x86PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component Component Id=x64RegEntPFWConfig Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes RegistryValue Id=x64PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component /Directory /Directory /Directory /Directory It creates the registry entry as : Is it possible that the slash after config in the above path can be done away witth and the key value is C:\Energy Solutions International\PFWService\config -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Creating Registry Key
Hi All, May be this is a trivial question to ask, but below is what i want to achieve: I am creating registry entries as below in WIX source file: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutionsConfig' Name=Energy Solutions International Directory Id='PFWServiceFolder' Name='PFWService' Directory Id='CONFIG' Name='config' Component Id=x86RegEntPFWConfig Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no RegistryValue Id=x86PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component Component Id=x64RegEntPFWConfig Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes RegistryValue Id=x64PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component /Directory /Directory /Directory /Directory It creates the registry entry as : Is it possible that the slash after config in the above path can be done away with and the key value is C:\Energy Solutions International\PFWService\config instead, or the one created is the correct one. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] (Ignore)Fwd: Registry key created
Sorry for the redundant post, just happened by typo...ignore this one. Original Message Subject:Registry key created Date: Fri, 13 Dec 2013 11:10:41 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Hi All, I am creating registry entries as below in WIX source file: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutionsConfig' Name=Energy Solutions International Directory Id='PFWServiceFolder' Name='PFWService' Directory Id='CONFIG' Name='config' Component Id=x86RegEntPFWConfig Guid=5DAD9B46-43BB-42D2-91E9-F2248369AA68 Win64=no RegistryValue Id=x86PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component Component Id=x64RegEntPFWConfig Guid=57240178-4A44-4C6F-A11C-B4DE99573DE0 Win64=yes RegistryValue Id=x64PFWConfigRegValue Root=HKLM Key=SOFTWARE\[Manufacturer] Name=configPath *Value=[CONFIG]* Type=string / CreateFolder/ /Component /Directory /Directory /Directory /Directory It creates the registry entry as : Is it possible that the slash after config in the above path can be done away witth and the key value is C:\Energy Solutions International\PFWService\config -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Hi All, I just saw this behaviour. My installer creates the following :C:\Energy Solutions International\PFWService\config, if this path is open and i run the uninstall from control panel, then the path remains(C:\Energy Solutions International\PFWService\config) although files under it is removed. Is it expected behavior or incorrect. If incorrect what is the workaround for the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fwd: Getting error notification when running .msi Installer
Please let me know if someone has any idea on this. Original Message Subject:Getting error notification when running .msi Installer Date: Mon, 02 Dec 2013 11:02:25 +0530 From: Suvrajyoti Panda suvrajyo...@contata.co.in To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Hi All, I have created a .msi installer using WIX. When i execute the installer through command line it installs the application without any error messages but when it i do it through clicking the setup that gets created: MyWebSetup.msi, i am getting the below error message. There is no error that gets logged in the log file though. I am not able to see errors in the log file as well. When i looked into the event viewer i am seeing this message below:Product: /Pipeline Framework Service Client -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action MakeWepApp40, location: C:\EnergySolutionsInternational\PipelineFrameworkService\PFWWebSite\, command: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -norestart -s W3SVC/1/ROOT/PFWServiceApplication / And in my product.wxs file i have the below entries: !-- .NET Framework 3.0 SP 1 must be installed -- Property Id=FRAMEWORKBASEPATH RegistrySearch Id=FindFrameworkDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Name=InstallRoot Type=raw/ /Property Property Id=ASPNETREGIIS DirectorySearch Path=[FRAMEWORKBASEPATH] Depth=4 Id=FindAspNetRegIis FileSearch Name=aspnet_regiis.exe MinVersion=4.0.0/ /DirectorySearch /Property !-- Switch ASP.NET to version 4.0 -- CustomAction Id=MakeWepApp40 Directory=MYWEBWEBSITE ExeCommand=[ASPNETREGIIS] -norestart -s W3SVC/1/ROOT/[WEB_APP_NAME] Return=check Not Installed /CustomAction InstallExecuteSequence Custom Action=MakeWepApp40 After=InstallFinalizeASPNETREGIIS AND NOT Installed/Custom /InstallExecuteSequence !-- Specify UI -- UIRef Id=MyWebUI / I am not able to figure here though what the problem is. Could you guys please help me on this, i am stuck here. Please let me know if any other input is required. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fwd: Getting error notification when running .msi Installer
Hi Blair, Yes i needed to do that and was able to solve the issue. Thanks Regards, SuvraJyoti On 02-12-2013 22:07, Blair Murri wrote: Was your command prompt elevated? Do you need to make your custom action deferred with impersonation turned off? -Blair Date: Mon, 2 Dec 2013 19:53:13 +0530 From: suvrajyo...@contata.co.in To: wix-users@lists.sourceforge.net Subject: [WiX-users] Fwd: Getting error notification when running .msi Installer Please let me know if someone has any idea on this. Original Message Subject: Getting error notification when running .msi Installer Date:Mon, 02 Dec 2013 11:02:25 +0530 From:Suvrajyoti Panda suvrajyo...@contata.co.in To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Hi All, I have created a .msi installer using WIX. When i execute the installer through command line it installs the application without any error messages but when it i do it through clicking the setup that gets created: MyWebSetup.msi, i am getting the below error message. There is no error that gets logged in the log file though. I am not able to see errors in the log file as well. When i looked into the event viewer i am seeing this message below:Product: /Pipeline Framework Service Client -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action MakeWepApp40, location: C:\EnergySolutionsInternational\PipelineFrameworkService\PFWWebSite\, command: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -norestart -s W3SVC/1/ROOT/PFWServiceApplication / And in my product.wxs file i have the below entries: !-- .NET Framework 3.0 SP 1 must be installed -- Property Id=FRAMEWORKBASEPATH RegistrySearch Id=FindFrameworkDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Name=InstallRoot Type=raw/ /Property Property Id=ASPNETREGIIS DirectorySearch Path=[FRAMEWORKBASEPATH] Depth=4 Id=FindAspNetRegIis FileSearch Name=aspnet_regiis.exe MinVersion=4.0.0/ /DirectorySearch /Property !-- Switch ASP.NET to version 4.0 -- CustomAction Id=MakeWepApp40 Directory=MYWEBWEBSITE ExeCommand=[ASPNETREGIIS] -norestart -s W3SVC/1/ROOT/[WEB_APP_NAME] Return=check Not Installed /CustomAction InstallExecuteSequence Custom Action=MakeWepApp40 After=InstallFinalizeASPNETREGIIS AND NOT Installed/Custom /InstallExecuteSequence !-- Specify UI -- UIRef Id=MyWebUI / I am not able to figure here though what the problem is. Could you guys please help me on this, i am stuck here. Please let me know if any other input is required. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Getting error notification when running .msi Installer
Hi All, I have created a .msi installer using WIX. When i execute the installer through command line it installs the application without any error messages but when it i do it through clicking the setup that gets created: MyWebSetup.msi, i am getting the below error message. There is no error that gets logged in the log file though. I am not able to see errors in the log file as well. When i looked into the event viewer i am seeing this message below:Product: /Pipeline Framework Service Client -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action MakeWepApp40, location: C:\EnergySolutionsInternational\PipelineFrameworkService\PFWWebSite\, command: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -norestart -s W3SVC/1/ROOT/PFWServiceApplication / And in my product.wxs file i have the below entries: !-- .NET Framework 3.0 SP 1 must be installed -- Property Id=FRAMEWORKBASEPATH RegistrySearch Id=FindFrameworkDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Name=InstallRoot Type=raw/ /Property Property Id=ASPNETREGIIS DirectorySearch Path=[FRAMEWORKBASEPATH] Depth=4 Id=FindAspNetRegIis FileSearch Name=aspnet_regiis.exe MinVersion=4.0.0/ /DirectorySearch /Property !-- Switch ASP.NET to version 4.0 -- CustomAction Id=MakeWepApp40 Directory=MYWEBWEBSITE ExeCommand=[ASPNETREGIIS] -norestart -s W3SVC/1/ROOT/[WEB_APP_NAME] Return=check Not Installed /CustomAction InstallExecuteSequence Custom Action=MakeWepApp40 After=InstallFinalizeASPNETREGIIS AND NOT Installed/Custom /InstallExecuteSequence !-- Specify UI -- UIRef Id=MyWebUI / I am not able to figure here though what the problem is. Could you guys please help me on this, i am stuck here. Please let me know if any other input is required. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Unable to switch ASP.NET to version 4.0
Hi All,
I am trying to set the asp.net version to 4.0. I have below piece of
code in my product.wxs :
Switch ASP.NET to version 4.0:
!-- Switch ASP.NET to version 4.0 --
CustomAction Id=MakeWepApp40 Directory=MYWEBWEBSITE
ExeCommand=[ASPNETREGIIS] -norestart -s
W3SVC/MyWebSiteId/ROOT/[WEB_APP_NAME] Return=check/
InstallExecuteSequence
Custom Action=MakeWepApp40 After=InstallFinalize
ASPNETREGIIS AND NOT Installed/Custom
/InstallExecuteSequence
The installer gets created but throws the below error :
I believe its is because of some issue here that this is occurring as on
commenting this part the installer got created but the app pool was not
set for the application.
The product.wxs also references the iisconfiguration.wxs that looks like
below:
DirectoryRef Id=MYWEBWEBSITE
!-- Configuring app pool --
Component Id=MyWebAppPoolCmp Guid= KeyPath=yes
iis:WebAppPool Id=MyWebAppPool Name=[WEB_APP_NAME] /
/Component
!-- Configure virtual dir --
Component Id=MyWebVirtualDirCmp
Guid={751DEB01-ECC1-48ff-869A-65BCEE9E0528} KeyPath=yes
iis:WebServiceExtension Id=ExtensionASP2
Group=ASP.NET v2.0.50727 Allow=yes
File=[NETFRAMEWORK20INSTALLROOTDIR]aspnet_isapi.dll
Description=ASP.NET v2.0.50727/
iis:WebVirtualDir Id=MyWebVirtualDir
Alias=[VIRTUAL_DIR_VAL] Directory=MYWEBWEBSITE WebSite=DefaultWebSite
iis:WebDirProperties Id=MyWebVirtDirProperties
AnonymousAccess=yes BasicAuthentication=yes
WindowsAuthentication=yes /
iis:WebApplication Id=MyWebWebApplication
Name=[VIRTUAL_DIR_VAL] /
/iis:WebVirtualDir
/Component
/DirectoryRef
Could someone suggest whats the issue here?
Regards,
SuvraJyoti
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing specific folders only
Hi Carter, I cannot change the directory structure to put data in the app folder. I want it in the location C:\Energy Solutions\PipelineOptimizer only. Is there anyway that i can while generating the source file for data directory using heat (trunkdata.wxs) all the components inside the trunkdata.wxs to have the attribute permanent = yes. This would have been the simplest of solutions. Please let me know if you have any pointers on the same. Regards, Suvra Jyoti On 22-11-2013 19:59, Carter Young wrote: Restructure the Setup to put the Data in the AppData Folder. If this is a corporate install, leaving it behind is OK, as employees won't know its there. If it's for public Consumption, the AppData Folder is the Accepted Practice. Create the Directory Structure, then add the Components inside the Directory, one after the other, marking each component as Key. Then Mark the Directory as permanent, like you have done. In Windows Parlance, leaving a folder behind without asking is usually frowned upon. Carter Quoting Suvrajyoti Panda suvrajyo...@contata.co.in: Hi, Just to add, I have tried setting one of components manually as permanent=yes in the wxs file of the data directory(trunkdata.wxs, i have created this by heat). This seems to leave the folder structure and component that i marked a permanent. Is there a way in heat that i can assign the attribute permanent=yes to all the components generated? Regards, SuvraJyoti On 22-11-2013 16:15, Suvrajyoti Panda wrote: Hi Carter, This does not work in the first place as Directory element is not supported inside a Component. Moreover i need that only the data directory be left behind on uninstall. Reiterating once more if i have not specified correctly earlier: Under C:\Energy Solutions(Not using x86 anymore as ealier)\PipelineOptimizer there are four folders are created by installer under : data, db, engine , security.On uninstallation i want that only the data folder should be left behind. So finally i should have only data folder under C:\Energy Solutions\PipelineOptimizer. Please let me know if there is some other way. Regards, SuvraJyoti On 21-11-2013 23:44, Carter Young wrote: Do Like So: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 Directory Id='AppDataFolder' Directory Id='TORTDEMODATA' Name='PipelineOptimizer 6.0.0' RemoveFolder Id='TORTDEMO' On='uninstall'/ This puts the Data Directory in C:\Users\UserName\Local\AppData and sgould leave it after uninstall. Quoting Suvrajyoti Panda suvrajyo...@contata.co.in: Hi Guys, I have created an installer in WIX that creates the below directory structure : The structure that i have used in main .wxs file is as below: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 RemoveFolder Id='TORTDEMO' On='uninstall'/ /Component No what happens when i uninstall is that the whole Energy Solutions folder gets uninstalled. I do not want that to happen. I want that the structure C:\Program Files (x86)\Energy Solutions\PipelineOptimizer 6.0.0 should be there and when i uninstall then only the 'data' directory should remain. Please let me know how do i achieve the same. Thanks in advance. Regards, Suvra Jyoti -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists
[WiX-users] Applying XSL transform to add permanent attribute for Components.
Hi All,
I have a .wxs file like trundata.wxs that i have generated through heat
command below:
heat dir D:\Project\ESI\Code\trunk\data -cg trunkdata -gg -ke -sfrag
-dr TORTDEMO -var var.TrunkDataPath -t C:\test\HeatXSL.xslt -out
trunkdata.wxs.
As evident from above command i am using an XSL transform to with the
XSLt file below to add permanent attribute = yes:
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:wix=http://schemas.microsoft.com/wix/2006/wi;
xmlns=http://schemas.microsoft.com/wix/2006/wi;
exclude-result-prefixes=xsl wix
xsl:output method=xml indent=yes omit-xml-declaration=yes /
xsl:strip-space elements=*/
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template
match=@Permanent[parent::wix:Component[parent::wix:Directory[parent::wix:DirectoryRef[parent::wix:Fragment[parent::wix:WIX]
xsl:attribute name=Permanent
xsl:value-of select='yes'/
/xsl:attribute
/xsl:template
/xsl:stylesheet
Even after applying this transform i am getting the below structure of
trundata.wxs without the permanent attribute:
Fragment
DirectoryRef Id=TORTDEMO
Directory Id=dirEC9F969BD29B8C21CDD08465AEB03AA5
Name=data
Component Id=cmpAE260E64AA13C102D822FA2BC8EFE4B4
Guid={8C55B2F9-E62F-4F7E-A2D7-25016D76A5F0}
File Id=fil519D18F66CAEB815FCB031BB142F4545
KeyPath=yes Source=$(var.TrunkDataPath)\DEFAULT_MGRAPH_LINES.BDB /
/Component
Component Id=cmpEE90C259D53A9FD8B8B1745D8892DABA
Guid={0AC90701-59CF-4F4A-A5E4-D47C8C82FD0B}
File Id=filE45BEC205C0153C2E223C0CD332B31DD
KeyPath=yes Source=$(var.TrunkDataPath)\DEFAULT_MGRAPH_LIST.BDB /
/Component
Please let me know if you have any pointers on the same.
Regards,
SuvraJyoti
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Applying XSL transform to add permanent attribute for Components.
Got the solution...just changed my xslt as below and it generated the
trunkdata.wxs file with all the permanent attributes set to yes.
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:wix=http://schemas.microsoft.com/wix/2006/wi;
xmlns=http://schemas.microsoft.com/wix/2006/wi;
exclude-result-prefixes=xsl wix
xsl:output method=xml indent=yes omit-xml-declaration=yes /
xsl:strip-space elements=*/
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
!-- add permanent=yes attribute to component --
xsl:template match=wix:Component
xsl:copy
!-- add attribute --
xsl:attribute name=Permanentyes/xsl:attribute
!-- copy component as is --
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
/xsl:stylesheet
On 25-11-2013 11:23, Suvrajyoti Panda wrote:
Hi All,
I have a .wxs file like trundata.wxs that i have generated through
heat command below:
heat dir D:\Project\ESI\Code\trunk\data -cg trunkdata -gg -ke -sfrag
-dr TORTDEMO -var var.TrunkDataPath -t C:\test\HeatXSL.xslt -out
trunkdata.wxs.
As evident from above command i am using an XSL transform to with the
XSLt file below to add permanent attribute = yes:
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:wix=http://schemas.microsoft.com/wix/2006/wi;
xmlns=http://schemas.microsoft.com/wix/2006/wi;
exclude-result-prefixes=xsl wix
xsl:output method=xml indent=yes omit-xml-declaration=yes /
xsl:strip-space elements=*/
xsl:template match=@*|node()
xsl:copy
xsl:apply-templates select=@*|node()/
/xsl:copy
/xsl:template
xsl:template
match=@Permanent[parent::wix:Component[parent::wix:Directory[parent::wix:DirectoryRef[parent::wix:Fragment[parent::wix:WIX]
xsl:attribute name=Permanent
xsl:value-of select='yes'/
/xsl:attribute
/xsl:template
/xsl:stylesheet
Even after applying this transform i am getting the below structure of
trundata.wxs without the permanent attribute:
Fragment
DirectoryRef Id=TORTDEMO
Directory Id=dirEC9F969BD29B8C21CDD08465AEB03AA5
Name=data
Component Id=cmpAE260E64AA13C102D822FA2BC8EFE4B4
Guid={8C55B2F9-E62F-4F7E-A2D7-25016D76A5F0}
File Id=fil519D18F66CAEB815FCB031BB142F4545
KeyPath=yes Source=$(var.TrunkDataPath)\DEFAULT_MGRAPH_LINES.BDB /
/Component
Component Id=cmpEE90C259D53A9FD8B8B1745D8892DABA
Guid={0AC90701-59CF-4F4A-A5E4-D47C8C82FD0B}
File Id=filE45BEC205C0153C2E223C0CD332B31DD
KeyPath=yes Source=$(var.TrunkDataPath)\DEFAULT_MGRAPH_LIST.BDB /
/Component
Please let me know if you have any pointers on the same.
Regards,
SuvraJyoti
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing specific folders only
Thanks Carter foe all the inputs. I have solved this issue by applying xslt transform to the heat ouput by adding the below to my xslt file: xsl:template match=wix:Component xsl:copy !-- add attribute -- xsl:attribute name=Permanentyes/xsl:attribute !-- copy component as is -- xsl:apply-templates select=@*|node()/ /xsl:copy /xsl:template Regards, SuvraJyoti On 25-11-2013 10:19, Suvrajyoti Panda wrote: Hi Carter, I cannot change the directory structure to put data in the app folder. I want it in the location C:\Energy Solutions\PipelineOptimizer only. Is there anyway that i can while generating the source file for data directory using heat (trunkdata.wxs) all the components inside the trunkdata.wxs to have the attribute permanent = yes. This would have been the simplest of solutions. Please let me know if you have any pointers on the same. Regards, Suvra Jyoti On 22-11-2013 19:59, Carter Young wrote: Restructure the Setup to put the Data in the AppData Folder. If this is a corporate install, leaving it behind is OK, as employees won't know its there. If it's for public Consumption, the AppData Folder is the Accepted Practice. Create the Directory Structure, then add the Components inside the Directory, one after the other, marking each component as Key. Then Mark the Directory as permanent, like you have done. In Windows Parlance, leaving a folder behind without asking is usually frowned upon. Carter Quoting Suvrajyoti Panda suvrajyo...@contata.co.in: Hi, Just to add, I have tried setting one of components manually as permanent=yes in the wxs file of the data directory(trunkdata.wxs, i have created this by heat). This seems to leave the folder structure and component that i marked a permanent. Is there a way in heat that i can assign the attribute permanent=yes to all the components generated? Regards, SuvraJyoti On 22-11-2013 16:15, Suvrajyoti Panda wrote: Hi Carter, This does not work in the first place as Directory element is not supported inside a Component. Moreover i need that only the data directory be left behind on uninstall. Reiterating once more if i have not specified correctly earlier: Under C:\Energy Solutions(Not using x86 anymore as ealier)\PipelineOptimizer there are four folders are created by installer under : data, db, engine , security.On uninstallation i want that only the data folder should be left behind. So finally i should have only data folder under C:\Energy Solutions\PipelineOptimizer. Please let me know if there is some other way. Regards, SuvraJyoti On 21-11-2013 23:44, Carter Young wrote: Do Like So: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 Directory Id='AppDataFolder' Directory Id='TORTDEMODATA' Name='PipelineOptimizer 6.0.0' RemoveFolder Id='TORTDEMO' On='uninstall'/ This puts the Data Directory in C:\Users\UserName\Local\AppData and sgould leave it after uninstall. Quoting Suvrajyoti Panda suvrajyo...@contata.co.in: Hi Guys, I have created an installer in WIX that creates the below directory structure : The structure that i have used in main .wxs file is as below: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 RemoveFolder Id='TORTDEMO' On='uninstall'/ /Component No what happens when i uninstall is that the whole Energy Solutions folder gets uninstalled. I do not want that to happen. I want that the structure C:\Program Files (x86)\Energy Solutions\PipelineOptimizer 6.0.0 should be there and when i uninstall then only the 'data' directory should remain. Please let me know how do i achieve the same. Thanks in advance. Regards, Suvra Jyoti -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free
Re: [WiX-users] Removing specific folders only
Hi Carter, This does not work in the first place as Directory element is not supported inside a Component. Moreover i need that only the data directory be left behind on uninstall. Reiterating once more if i have not specified correctly earlier: Under C:\Energy Solutions(Not using x86 anymore as ealier)\PipelineOptimizer there are four folders are created by installer under : data, db, engine , security.On uninstallation i want that only the data folder should be left behind. So finally i should have only data folder under C:\Energy Solutions\PipelineOptimizer. Please let me know if there is some other way. Regards, SuvraJyoti On 21-11-2013 23:44, Carter Young wrote: Do Like So: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 Directory Id='AppDataFolder' Directory Id='TORTDEMODATA' Name='PipelineOptimizer 6.0.0' RemoveFolder Id='TORTDEMO' On='uninstall'/ This puts the Data Directory in C:\Users\UserName\Local\AppData and sgould leave it after uninstall. Quoting Suvrajyoti Panda suvrajyo...@contata.co.in: Hi Guys, I have created an installer in WIX that creates the below directory structure : The structure that i have used in main .wxs file is as below: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 RemoveFolder Id='TORTDEMO' On='uninstall'/ /Component No what happens when i uninstall is that the whole Energy Solutions folder gets uninstalled. I do not want that to happen. I want that the structure C:\Program Files (x86)\Energy Solutions\PipelineOptimizer 6.0.0 should be there and when i uninstall then only the 'data' directory should remain. Please let me know how do i achieve the same. Thanks in advance. Regards, Suvra Jyoti -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing specific folders only
Hi, Just to add, I have tried setting one of components manually as permanent=yes in the wxs file of the data directory(trunkdata.wxs, i have created this by heat). This seems to leave the folder structure and component that i marked a permanent. Is there a way in heat that i can assign the attribute permanent=yes to all the components generated? Regards, SuvraJyoti On 22-11-2013 16:15, Suvrajyoti Panda wrote: Hi Carter, This does not work in the first place as Directory element is not supported inside a Component. Moreover i need that only the data directory be left behind on uninstall. Reiterating once more if i have not specified correctly earlier: Under C:\Energy Solutions(Not using x86 anymore as ealier)\PipelineOptimizer there are four folders are created by installer under : data, db, engine , security.On uninstallation i want that only the data folder should be left behind. So finally i should have only data folder under C:\Energy Solutions\PipelineOptimizer. Please let me know if there is some other way. Regards, SuvraJyoti On 21-11-2013 23:44, Carter Young wrote: Do Like So: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 Directory Id='AppDataFolder' Directory Id='TORTDEMODATA' Name='PipelineOptimizer 6.0.0' RemoveFolder Id='TORTDEMO' On='uninstall'/ This puts the Data Directory in C:\Users\UserName\Local\AppData and sgould leave it after uninstall. Quoting Suvrajyoti Panda suvrajyo...@contata.co.in: Hi Guys, I have created an installer in WIX that creates the below directory structure : The structure that i have used in main .wxs file is as below: Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Directory Id='EnergySolutions' Name='Energy Solutions' Directory Id='TORTDEMO' Name='PipelineOptimizer 6.0.0' Component Id=FOLDERTOREMOVE Guid=9D5FEECE-74FE-45A2-BD34-41562EC8ED16 RemoveFolder Id='TORTDEMO' On='uninstall'/ /Component No what happens when i uninstall is that the whole Energy Solutions folder gets uninstalled. I do not want that to happen. I want that the structure C:\Program Files (x86)\Energy Solutions\PipelineOptimizer 6.0.0 should be there and when i uninstall then only the 'data' directory should remain. Please let me know how do i achieve the same. Thanks in advance. Regards, Suvra Jyoti -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fwd: Re: Referring to fragments
Hi John/All,
I have used the below commands:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag -dr
TORTDEMO -out trunkdb.wxs
candle TortEngineDemo.wxs trunkdb.wxs
light -b D:\Project\ESI\Code\trunk\db -out TrunkDBDemo.msi
TortEngineDemo.wixobj trunkdb.wixobj
This does create the TrunkDBDemo.msi and when i run it it also creates
the Tort Demo folder on the desktop and the db directory in which i
can find all the files that were there in the source directory. The
required registry entry is also created.
The change i have done is added the part /-b
D:\Project\ESI\Code\trunk\db /to the Light command/.
///
But the Light does throw up some many errors such as :
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(921) : error
LGHT0204 :
ICE38: Component cmp159DEBB341761ACFD08D530D4AB638B2 installs to user
profile. It must use a registry key under HKCU as its KeyPath, not a file.
In the trunkdb.wxs file i have the like below(files are attached)
Component Id=cmp159DEBB341761ACFD08D530D4AB638B2
Guid={AA11F234-AF77-4F2C-B4A2-355A25C71234}
File Id=fil13F4C3BF2526AB7CCACA852D90DAA880
KeyPath=yes Source=SourceDir\alarm.db/
Do i need to change this file to registry key when generating this file
from heat? Please suggest as to what the error could be for?
Regards,
Suvra Jyoti
On 18-11-2013 21:31, John Ludlow wrote:
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.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
Re: [WiX-users] Fwd: Re: Referring to fragments
Hi John,
Thanks for the help...Just followed the steps...worked like a charm. The
folder got installed into the program files folder and there were no
errors thrown by Light.
But I want the db directory to be created into a folder in say
c:\[FolderName](c:\[FolderName]\Tort Demo). I have tried with like as
mentioned earlier DesktopFolder, LocalAppdatafolder etc just to see if
everything goes fine but i was getting the error mentioned in below mail.
For those errors i landed on to
http://robmensching.com/blog/posts/2007/4/27/how-to-create-an-uninstall-shortcut-and-pass-all-the
where it is said that the registry key is created to make ICE18
http://msdn2.microsoft.com/en-us/library/aa368942.aspx, ICE38
http://msdn2.microsoft.com/en-us/library/aa368961.aspx and ICE48
http://msdn2.microsoft.com/en-us/library/aa368977.aspx happy. So can i
ignore those errors and move ahead?
How can i get my directory created to c:\[FolderName]\ ?
Regards,
SuvraJyoti
On 19-11-2013 14:05, John Ludlow wrote:
That should have read:
If you make this change, you can also remove the following line:
RegistryValue Root='HKCU' Key='Software\[Manufacturer]\[ProductName]'
Type='string' Value='' KeyPath='yes' /
On 19 November 2013 08:34, John Ludlow john.ludlow...@gmail.com
mailto:john.ludlow...@gmail.com wrote:
That's because of this:
Directory Id='DesktopFolder' Name='PFiles'
This will put files on the users desktop - are you sure that's
what you want? (Hint: it's probably not) Change this to
ProgramFilesFolder (or ProgramFiles64Folder). Remember how you
were getting a similar error previously?
If you make this change, you can also remove the following line:
Alternatively, use a script to modify each component so it
contains a registry entry.
On 19 November 2013 07:50, Suvrajyoti Panda
suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote:
Hi John/All,
I have used the below commands:
heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag
-dr TORTDEMO -out trunkdb.wxs
candle TortEngineDemo.wxs trunkdb.wxs
light -b D:\Project\ESI\Code\trunk\db -out TrunkDBDemo.msi
TortEngineDemo.wixobj trunkdb.wixobj
This does create the TrunkDBDemo.msi and when i run it it also
creates the Tort Demo folder on the desktop and the db
directory in which i can find all the files that were there in
the source directory. The required registry entry is also created.
The change i have done is added the part /-b
D:\Project\ESI\Code\trunk\db /to the Light command/.
/
But the Light does throw up some many errors such as :
C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(921) :
error LGHT0204 :
ICE38: Component cmp159DEBB341761ACFD08D530D4AB638B2 installs
to user profile. It must use a registry key under HKCU as its
KeyPath, not a file.
In the trunkdb.wxs file i have the like below(files are attached)
Component Id=cmp159DEBB341761ACFD08D530D4AB638B2
Guid={AA11F234-AF77-4F2C-B4A2-355A25C71234}
File
Id=fil13F4C3BF2526AB7CCACA852D90DAA880 KeyPath=yes
Source=SourceDir\alarm.db/
Do i need to change this file to registry key when generating
this file from heat? Please suggest as to what the error could
be for?
Regards,
Suvra Jyoti
On 18-11-2013 21:31, John Ludlow wrote:
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
Re: [WiX-users] Fwd: Re: Referring to fragments
Ok, I have made the following changes to the TortEngineDemo.wxs(also they are attached): Directory Id='TARGETDIR' Name='SourceDir' Directory Id='MyFolder' Name='EnergySolutionsInternational' FileSource='D:\' 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 !--Component Id=test Guid=A90AAE4F-CEB3-4958-A97D-458B25800D23 File Id=test KeyPath=no Source=C:\Users\suvrajyotip\Desktop\test.txt / RegistryValue Key=Software\[Manufacturer]\[ProductName]_Dummy Root=HKCU KeyPath='yes' Type='string' Value=''/ /Component-- /Directory /Directory When i execute Candle and Light, the msi gets created and when i run the msi, the directory structure gets created in D:\EnergySolutionsInternational\Tort demo On uninstalling the EnergySolutionsInternational directory also gets removed. Do you think that should be the behaviour.? On 19-11-2013 15:44, John Ludlow wrote: In theory, just removing this line should do it: Directory Id='DesktopFolder' Name='PFiles' I haven't tried that though, so I'm not 100% sure. If not, you can also try a custom action which sets the directory. Generally, you should think twice before dropping files directly under c:\ - most people like to keep that as clean as possible. On 19 November 2013 09:27, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Hi John, Thanks for the help...Just followed the steps...worked like a charm. The folder got installed into the program files folder and there were no errors thrown by Light. But I want the db directory to be created into a folder in say c:\[FolderName](c:\[FolderName]\Tort Demo). I have tried with like as mentioned earlier DesktopFolder, LocalAppdatafolder etc just to see if everything goes fine but i was getting the error mentioned in below mail. For those errors i landed on to http://robmensching.com/blog/posts/2007/4/27/how-to-create-an-uninstall-shortcut-and-pass-all-the where it is said that the registry key is created to make ICE18 http://msdn2.microsoft.com/en-us/library/aa368942.aspx, ICE38 http://msdn2.microsoft.com/en-us/library/aa368961.aspx and ICE48 http://msdn2.microsoft.com/en-us/library/aa368977.aspx happy. So can i ignore those errors and move ahead? How can i get my directory created to c:\[FolderName]\ ? Regards, SuvraJyoti On 19-11-2013 14:05, John Ludlow wrote: That should have read: If you make this change, you can also remove the following line: RegistryValue Root='HKCU' Key='Software\[Manufacturer]\[ProductName]' Type='string' Value='' KeyPath='yes' / On 19 November 2013 08:34, John Ludlow john.ludlow...@gmail.com mailto:john.ludlow...@gmail.com wrote: That's because of this: Directory Id='DesktopFolder' Name='PFiles' This will put files on the users desktop - are you sure that's what you want? (Hint: it's probably not) Change this to ProgramFilesFolder (or ProgramFiles64Folder). Remember how you were getting a similar error previously? If you make this change, you can also remove the following line: Alternatively, use a script to modify each component so it contains a registry entry. On 19 November 2013 07:50, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Hi John/All, I have used the below commands: heat dir D:\Project\ESI\Code\trunk\db -cg trunkdb -gg -sfrag -dr TORTDEMO -out trunkdb.wxs candle TortEngineDemo.wxs trunkdb.wxs light -b D:\Project\ESI\Code\trunk\db -out TrunkDBDemo.msi TortEngineDemo.wixobj trunkdb.wixobj This does create the TrunkDBDemo.msi and when i run it it also creates the Tort Demo folder on the desktop and the db directory in which i can find all the files that were there in the source directory. The required registry entry is also created. The change i have done is added the part /-b D:\Project\ESI\Code\trunk\db /to the Light command/. / But the Light does throw up some many errors such as : C:\Program Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(921) : error LGHT0204 : ICE38: Component cmp159DEBB341761ACFD08D530D4AB638B2 installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. In the trunkdb.wxs file i have the like below(files
Re: [WiX-users] Fwd: Re: Referring to fragments
Hey John, Thanks for all the help you provided to me on my issues. I do not currently have this book but would get it ASAP(ebook) Thanks once again and look forward to your guidance. Regards, SuvraJyoti On 19-11-2013 16:29, John Ludlow wrote: That looks like expected behaviour to me. What's happening here is that the installer's created that directory structure and deployed a bunch of resources. During uninstall, it determines that those are the files it deployed and removes them. you can specify Component/@Permanent=yes if you want to change that. Once it's removed all the files, it finds that the directory is empty and removes that as well. Do you have a copy of this book? It's a great reference for understanding WiX concepts. http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book On 19 November 2013 10:22, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Ok, I have made the following changes to the TortEngineDemo.wxs(also they are attached): Directory Id='TARGETDIR' Name='SourceDir' Directory Id='MyFolder' Name='EnergySolutionsInternational' FileSource='D:\' 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 !--Component Id=test Guid=A90AAE4F-CEB3-4958-A97D-458B25800D23 File Id=test KeyPath=no Source=C:\Users\suvrajyotip\Desktop\test.txt / RegistryValue Key=Software\[Manufacturer]\[ProductName]_Dummy Root=HKCU KeyPath='yes' Type='string' Value=''/ /Component-- /Directory /Directory When i execute Candle and Light, the msi gets created and when i run the msi, the directory structure gets created in D:\EnergySolutionsInternational\Tort demo On uninstalling the EnergySolutionsInternational directory also gets removed. Do you think that should be the behaviour.? On 19-11-2013 15:44, John Ludlow wrote: In theory, just removing this line should do it: Directory Id='DesktopFolder' Name='PFiles' I haven't tried that though, so I'm not 100% sure. If not, you can also try a custom action which sets the directory. Generally, you should think twice before dropping files directly under c:\ - most people like to keep that as clean as possible. On 19 November 2013 09:27, Suvrajyoti Panda suvrajyo...@contata.co.in mailto:suvrajyo...@contata.co.in wrote: Hi John, Thanks for the help...Just followed the steps...worked like a charm. The folder got installed into the program files folder and there were no errors thrown by Light. But I want the db directory to be created into a folder in say c:\[FolderName](c:\[FolderName]\Tort Demo). I have tried with like as mentioned earlier DesktopFolder, LocalAppdatafolder etc just to see if everything goes fine but i was getting the error mentioned in below mail. For those errors i landed on to http://robmensching.com/blog/posts/2007/4/27/how-to-create-an-uninstall-shortcut-and-pass-all-the where it is said that the registry key is created to make ICE18 http://msdn2.microsoft.com/en-us/library/aa368942.aspx, ICE38 http://msdn2.microsoft.com/en-us/library/aa368961.aspx and ICE48 http://msdn2.microsoft.com/en-us/library/aa368977.aspx happy. So can i ignore those errors and move ahead? How can i get my directory created to c:\[FolderName]\ ? Regards, SuvraJyoti On 19-11-2013 14:05, John Ludlow wrote: That should have read: If you make this change, you can also remove the following line: RegistryValue Root='HKCU' Key='Software\[Manufacturer]\[ProductName]' Type='string' Value='' KeyPath='yes' / On 19 November 2013 08:34, John Ludlow john.ludlow...@gmail.com mailto:john.ludlow...@gmail.com wrote: That's because of this: Directory Id='DesktopFolder' Name='PFiles' This will put files on the users desktop - are you sure that's what you want? (Hint: it's probably not) Change this to ProgramFilesFolder (or ProgramFiles64Folder). Remember how you were getting a similar error previously? If you make this change, you can also remove the following line: Alternatively, use a script to modify each component so it contains a registry entry. On 19
Re: [WiX-users] Referring to fragments
which means MSI
won't know where to put it.
My advice would be to concentrate on getting a successful compilation, then
work from there. Keep compiling regularly as you work. If you see a
compilation failure, stop and deal with it. This makes it much easier to
deal with issues as you discover them.
Hope that helps
On 15 November 2013 11:13, Suvrajyoti Panda suvrajyo...@contata.co.inwrote:
Hi,
I have a fragment that i have created through Heat. Basically i want to
create a db directory that has db files inside it through the installer.
It has the structure as below:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Fragment
DirectoryRef Id=
Directory Id= Name=db
Component Id=cmpCB46AAB9A4F3EB62F8247A194B4BBB4B
Guid={DE25A51B-AD43-4C74-8F84-9336AAC18BA0}
File Id=fil8B6B2F5720D83AD50A3898087E4DADF1
KeyPath=yes Source=SourceDir\alarm.db /
/Component
.. many components follow here
.
.
.
/Directory
/DirectoryRef
/Fragment
/Wix
My main WiX installer file is as below:
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Name='Tort Demo 1.0'
Id='0A6A060C-20A5-4716-994D-BC728A904F27'
UpgradeCode='3F665FE5-D9A9-4C9E-B260-7D54970C99F3'
Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='Acme
Ltd.'
Package Id='*' Keywords='Installer' Description=Tort 1.0
Installer Comments='Tort Ltd.' Manufacturer='ESI Ltd.'
InstallerVersion='300' Languages='1033' Compressed='yes'
SummaryCodepage='1252' /
Media Id='1' Cabinet='Tort.cab' EmbedCab='yes' DiskPrompt=CD-ROM
#1 /
Property Id='DiskPrompt' Value=Tort Demo Installation [1] /
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='PersonalFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=TORTDEMO
Guid=8D286AB1-8C00-4A88-A7EB-C83BB92C480A
RemoveFolder Id='TORTDEMO' On='uninstall' /
/Component
/Directory
/Directory
/Directory
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
/Feature
/Product
*
** Fragment**
**DirectoryRef Id=TORTDEMO**
**/DirectoryRef**
** /Fragment*
/Wix
I have tried to reference as given in the bold, but the directory
structure does not get created when i run the .msi installer an i am
getting the error C:\Program Files (x86)\WiX Toolset
v3.7\bin\TortEngineDemo.wxs(15) : error LGHT0
204 : ICE38: Component TORTDEMO installs to user profile. It must use a
registry
key under HKCU as its KeyPath, not a file.
Please help..
Regards,
Suvra Jyoti
On 15-11-2013 16:28, uholeschak wrote:
I have two burn bundles (with different UpgradeCodes)
that contain the same MsiPackage, but with different versions (different
ProductCode).
When I install the first burn bundle all is working fine,
but when installing the second bundle nothing is happening (the
MsiPackage
is not installed).
Is there a way to force burn to update an existing MsiPackage?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-packages-in-different-burn-bundles-not-updated-tp7590668.html
Sent from the wix-users mailing list archive at Nabble.com.
--
DreamFactory - Open Source REST JSON Services for HTML5 Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
DreamFactory - Open Source REST JSON Services for HTML5 Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
DreamFactory - Open Source REST JSON Services for HTML5 Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any
[WiX-users] Fwd: Re: Referring to fragments
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.in
To: General discussion about the WiX toolset.
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;
Fragment
DirectoryRef Id=TORTDEMO
Directory Id=dir653F7E432DCA0892A253D0CEC7775D03
Name=db
Component Id=cmp159DEBB341761ACFD08D530D4AB638B2
Guid={F89E44FD-879E-4076-B1A9-4CC2DFDB9DF4}
File Id=fil13F4C3BF2526AB7CCACA852D90DAA880
KeyPath=yes Source=SourceDir\alarm.db /
/Component
Component Id=cmpB5B2B206AA7A6A0007EEC8D894834050
Guid={88DECB74-680F-4075-B764-4AE663664829}
File Id=fil34C37BE68FA25CF6AE6B3151F5727B4B
KeyPath=yes Source=SourceDir\batch.db /
/Component.
.
.
.
.
.
.
So here i have generated the DirectoryRef Id as suggested by you. Now in
the TortEngineDemo.wxs i am trying to refer it as below :
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Name='Tort Demo 1.0'
Id='5A1581BE-27C3-46A1-8699-4F1D642C97E0'
UpgradeCode='C54B7D5D-0E66-43E8-A770-C9750693F057'
Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='Acme
Ltd.'
Package Id='*' Keywords='Installer' Description=Tort 1.0
Installer Comments='Tort Ltd.' Manufacturer='ESI Ltd.'
InstallerVersion='100' Languages='1033' Compressed='yes'
SummaryCodepage='1252' /
Media Id='1' Cabinet='Tort.cab' EmbedCab='yes' DiskPrompt=CD-ROM
#1 /
Property Id='DiskPrompt' Value=Tort Demo Installation [1] /
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='DesktopFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=CmpTrunkDB
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
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
ComponentRef Id='cmp159DEBB341761ACFD08D530D4AB638B2'/
/Feature
/Product
!--Fragment
DirectoryRef Id=dir69CDC966F9D8B6EA694F96E169B0FBFF
/DirectoryRef
/Fragment--
/Wix
I have executed the candle as below:
/candle TortEngineDemo.wxs trunkdb.wxs/ -- this generates the WIXOBJ
files. Then i execute /light -out TrunkDBDemo.msi TortEngineDemo.wixobj
trunkdb.wixobj/. On this i am again getting multiple errors : C:\Program
Files (x86)\WiX Toolset v3.7\bin\trunkdb.wxs(1119) : error LGHT0267 :
Found orphaned Component 'cmp5FAA008684E68756F59591139AA72C60'. If
this is a P
roduct, every Component must have at least one parent Feature. To
include a Com
ponent in a Module, you must include it directly as a Component element
of the M
odule element or indirectly via ComponentRef, ComponentGroup, or
ComponentGroupR
ef elements.
I am sure i am not referring the fragment the right way. Please suggest
how i need to refer to the fragment from my installer. I am really stuck
and any help would be much appreciable. Let me know if you are on Skype,
that would be helpful.
Regards,
SuvraJyoti
Regards,
SuvraJyoti
On 15-11-2013 19:19, John Ludlow wrote:
I think you're getting confused between two separate issues. If you're
getting the ICE error, then that would stop the build from successfully
completing. You may be using an out of date version of your installer.
Because of that, I would suggest that you do the following
1. Resolve the ICE issue. You suppress it so that it doesn't get run, but
the better thing to do is usually to solve the error. In this case, that
means add a registry entry to the component and mark it as KeyPath=yes.
2. Determine whether your directory structure is getting added to your
install. You can do this in a number of ways - using Orca.exe or performing
an admin install are two of them. Based on your question, I can't see a
reference to anything in the Fragment which contains the harvested
Re: [WiX-users] Referring to fragments
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
mailto: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.in
mailto:suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
mailto:wix-users@lists.sourceforge.net, john.ludlow...@gmail.com
mailto: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
Source=SourceDir\alarm.db /
/Component
Component
Id=cmpB5B2B206AA7A6A0007EEC8D894834050
Guid={88DECB74-680F-4075-B764-4AE663664829}
File
Id=fil34C37BE68FA25CF6AE6B3151F5727B4B KeyPath=yes
Source=SourceDir\batch.db /
/Component.
.
.
.
.
.
.
So here i have generated the DirectoryRef Id as suggested by you.
Now in the TortEngineDemo.wxs i am trying
[WiX-users] Fwd: Fwd: Re: Referring to fragments
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
To: John Ludlow 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
To: John Ludlow john.ludlow...@gmail.com
CC: General discussion about the WiX toolset.
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 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
mailto: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.in
mailto:suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
wix-users@lists.sourceforge.net
mailto:wix-users@lists.sourceforge.net, john.ludlow...@gmail.com
mailto: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
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
[WiX-users] Referring to fragments
Hi,
I have a fragment that i have created through Heat. Basically i want to
create a db directory that has db files inside it through the installer.
It has the structure as below:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Fragment
DirectoryRef Id=
Directory Id= Name=db
Component Id=cmpCB46AAB9A4F3EB62F8247A194B4BBB4B
Guid={DE25A51B-AD43-4C74-8F84-9336AAC18BA0}
File Id=fil8B6B2F5720D83AD50A3898087E4DADF1
KeyPath=yes Source=SourceDir\alarm.db /
/Component
.. many components follow here
.
.
.
/Directory
/DirectoryRef
/Fragment
/Wix
My main WiX installer file is as below:
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Name='Tort Demo 1.0'
Id='0A6A060C-20A5-4716-994D-BC728A904F27'
UpgradeCode='3F665FE5-D9A9-4C9E-B260-7D54970C99F3'
Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='Acme
Ltd.'
Package Id='*' Keywords='Installer' Description=Tort 1.0
Installer Comments='Tort Ltd.' Manufacturer='ESI Ltd.'
InstallerVersion='300' Languages='1033' Compressed='yes'
SummaryCodepage='1252' /
Media Id='1' Cabinet='Tort.cab' EmbedCab='yes' DiskPrompt=CD-ROM
#1 /
Property Id='DiskPrompt' Value=Tort Demo Installation [1] /
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='PersonalFolder' Name='PFiles'
Directory Id='TORTDEMO' Name='Tort Demo'
Component Id=TORTDEMO
Guid=8D286AB1-8C00-4A88-A7EB-C83BB92C480A
RemoveFolder Id='TORTDEMO' On='uninstall' /
/Component
/Directory
/Directory
/Directory
Feature Id='Complete' Level='1'
ComponentRef Id='TORTDEMO' /
/Feature
/Product
*
** Fragment**
**DirectoryRef Id=TORTDEMO**
**/DirectoryRef**
** /Fragment*
/Wix
I have tried to reference as given in the bold, but the directory
structure does not get created when i run the .msi installer an i am
getting the error C:\Program Files (x86)\WiX Toolset
v3.7\bin\TortEngineDemo.wxs(15) : error LGHT0
204 : ICE38: Component TORTDEMO installs to user profile. It must use a
registry
key under HKCU as its KeyPath, not a file.
Please help..
Regards,
Suvra Jyoti
On 15-11-2013 16:28, uholeschak wrote:
I have two burn bundles (with different UpgradeCodes)
that contain the same MsiPackage, but with different versions (different
ProductCode).
When I install the first burn bundle all is working fine,
but when installing the second bundle nothing is happening (the MsiPackage
is not installed).
Is there a way to force burn to update an existing MsiPackage?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-packages-in-different-burn-bundles-not-updated-tp7590668.html
Sent from the wix-users mailing list archive at Nabble.com.
--
DreamFactory - Open Source REST JSON Services for HTML5 Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
DreamFactory - Open Source REST JSON Services for HTML5 Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
