Hi,
I have a installer(msi) created on the development machine with the
below specifications
1.Win 7(64 bit)
2.SQL Server 2008 R2 - SP2(32 Bit)
3.VS 2010
I have used the sql:SqlDatabase funcationality of creating Database
and executing *.sql scripts, this works on the development machine
What are the exact options you are using when reinstalling?
When I run the .MSI, all I do is dbl click on the .MSI file, I didn't run
it with any option.
I will run it with logging
On Tue, Feb 25, 2014 at 6:17 PM, John Ludlow john.ludlow...@gmail.comwrote:
Follow the instructions here:
Ravi,
Please provide verbose logging of where it is failing...
http://support.microsoft.com/kb/223300
The simplest way for logging a single session is to start the installer with
the /l switch
msiexec /i c:\path\to\myinstall.msi /l*v c:\path\to\myinstall.log
(thanks John)
Steve
No problemo :)
On 26 February 2014 13:17, Steven Ogilvie steven.ogil...@titus.com wrote:
Ravi,
Please provide verbose logging of where it is failing...
http://support.microsoft.com/kb/223300
The simplest way for logging a single session is to start the installer
with the /l switch
I recreated the .MSI file today, and reran the installation with the
following command:
msiexec /i
C:\Installs\WixWindowsService2012Setup\bin\Release\WixWindowsService2012Setup.msi
/l*v C:\Installs\WixWindowsService2012Setup\bin\Release\install.log.
It still overrides the config file, and this is
BTW, you did mention the scheduling in your original mail - I missed it. My
bad.
On 26 February 2014 15:39, John Ludlow john.ludlow...@gmail.com wrote:
Aha!
MSI (s) (00:64) [09:59:21:043]: File: C:\Program
Files\WixWindowsService2012\WixWindowsService2012.exe.config; To be
installed;
Aha!
MSI (s) (00:64) [09:59:21:043]: File: C:\Program
Files\WixWindowsService2012\WixWindowsService2012.exe.config; To be
installed; Won't patch;No existing file
MSI (s) (00:64) [09:59:21:043]: Source for file
'WixWindowsService2012.exe.config' is compressed
So why is there No
Hi John,
No existing file is because prior to it the installation removed the file
MSI (s) (00:9C) [09:59:20:624]: Executing op:
FileRemove(,FileName=WixWindowsService2012.exe.config,,ComponentId={blabla})
MSI (s) (00:9C) [09:59:20:626]: Verifying accessibility of file:
Um, yes.
Have you considered using *afterInstallExecute *or *afterInstallExecuteAgain
*instead?
On 26 February 2014 15:49, faujong fiefie.ni...@gmail.com wrote:
Hi John,
No existing file is because prior to it the installation removed the file
MSI (s) (00:9C) [09:59:20:624]: Executing op:
You should not have an Upgrade element and a MajorUpgrade element. You should
remove the Upgrade element.
Date: Wed, 26 Feb 2014 07:49:31 -0800
From: fiefie.ni...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to not copy a file in subsequent installations?
The general approach to doing this is to condition the uninstall of
the web site on UPGRADINGPRODUCTCODE so it doesn't get uninstalled if
it's being upgraded. If you already shipped the product it's too late
for that.
In the incoming upgrade you'd check for the existence of the web site
and do
1) Remove the Registry Key in the ARP Uninstall Registry location for the
productcode for the old bundle.
2) The active(upgrade) bundle is coded to execute the old(cached) bundle
with the -quiet -uninstall flags.
Your upgrade bundle should contain the final contents.
Current: A.msi, B.msi
Desired
when the bundle is started and cached(different than package cache), it
creates a BootstrapperApplicationData.xml in the cached folder.
You can parse this based on the PackageID to get the DisplayName.
--
View this message in context:
OK, thanks a mit.
I have to check why my old bootstrapped shows the UI when called by the new one.
What is with the InstallState of the bundle. Is the Property installed in
BeginDetect the correct one? Or do I have to check it with all packages and if
one is found I know, that the bundle is
Has anyone else had this issue??
have a bitmap that covers text/button/etc controls... launch your
bootstrapper, then hit the ALT key, do your controls go in the background
(behind the bitmap?)
Steve
anyone know of a work around???
STeve
--
View this message in context:
Thank you all for your replies.
@Sean:
If I remove the UpgradeVersion elements, it keeps all the installation, ie
when I go to Control Panel\Programs\Programs and Features, my installation
shows up multiple times, as many as the number of times I install.
@John:
When
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7592961/afterInstallExecute.jpg
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-not-copy-a-file-in-subsequent-installations-tp7592929p7592961.html
Sent from the wix-users
Hi, we package the lessons and give to users in the format of msi file using
wix installer. When users install/ Uninstall these lessons MSI file on their
PC's, I should able to log this information with date time MSI name into
text file( file needs to create if not exists) under location (per
Is this just for logging purposes? Is the normal MSI log not sufficient?
If it's not, then depending on your situation, there's a number of options:
* The XmlFile element in the Util extension can be tied to a component and
update a target file when that component is installed or uninstalled.
The below Directory element installs my Windows Service on c:\program
files\WixWindowsService2012.
How can I install it on a subfolder, ie c:\program
files\myCompany\WixWindowsService2012 ?
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFiles64Folder
Or use the Event Log since it should track installation events
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: John Ludlow [mailto:john.ludlow...@gmail.com]
Sent:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFiles64Folder
Directory Id=myCompany Name=myCompany
Directory Id=INSTALLFOLDER
Name=WixWindowsService2012 /
/Directory
Thanks, that works !
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-install-on-a-subfolder-tp7592965p7592968.html
Sent from the wix-users mailing list archive at Nabble.com.
I can reproduce a bug where releasing the Alt key doesn't clear the accelerator
key with WixStdBA.
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Wednesday, February 26, 2014 1:27 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] alt key in
sorry if I sound dimwitted... what does that have to do with controls going
into the background and the images into the foreground?
i.e. launch bootstrapper and I have a light gray background image to have
the full area of the bootstrapper dialog a light gray colour (couldn't see
how to change
As part of my bundle BA I'd like to conditionally install a MS HotFix. No
sense installing it if it's already installed.
1) How do I determine if it's installed?
2) Is chaining a .msu any different than a .msi?
--
View this message in context:
On 25-Feb-14 10:34, Phill Hogland wrote:
candle.exe(0,0): error CNDL0001: Stream is not a valid resource file.
Open the extension in ILSpy (etc) and make sure the name is what you're
expecting.
--
sig://boB
http://joyofsetup.com/
On 26-Feb-14 18:33, Hoover, Jacob wrote:
I can reproduce a bug where releasing the Alt key doesn't clear the
accelerator key with WixStdBA.
What does clear the accelerator key mean?
--
sig://boB
http://joyofsetup.com/
Hi,
I have added two msipackages element in Wix bundle.
Chain
MsiPackage DisplayName=Sample Installer Demo1 Id=msi_installer1
SourceFile=E:\SampleMSI1.msi
DownloadUrl= http://{URL}/SampleMSI1.msi; Compressed=no
Permanent=yes /
MsiPackage DisplayName=Sample Installer Demo2
Chain/@ParallelCache='yes'
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Saravanan [mailto:periyasa...@syncfusion.com]
Sent: Wednesday, February 26, 2014 10:24
30 matches
Mail list logo
