Re: [WiX-users] No progress in installation
Hi,
No. We don't have installed any antivirus in an effected machines. In fresh
machine also, we are getting an same error. Kindly can anyone look over this
problem and provide solution?
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 25 August 2014 11:22 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] No progress in installation
The error indicates The system cannot find the file specified. Do you have
an over-zealous Anti-Virus software running on the effected machines?
-Original Message-
From: Vadivel Natarajan [mailto:vadiv...@syncfusion.com]
Sent: Monday, August 25, 2014 12:04 PM
To: General discussion about the WiX toolset.
Subject: [WiX-users] No progress in installation
Hi,
we had created an installer using Bootstrapper and Burn with wix 3.7. In some
machines, our setup installation was not started. Setup installation was in a
starting state. No progress in installation.
We are getting the below error when we look at the log file.
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\Application_1.1.0.3.exe
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[0E6C:10D4][2014-08-13T12:03:59]i199: Detect complete, result: 0x0
[0E6C:10D4][2014-08-13T12:03:59]i300: Apply begin
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\ Application_1.1.0.3.exe
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[1240:15D8][2014-08-13T12:04:02]i360: Creating a system restore point.
[1240:15D8][2014-08-13T12:06:10]i361: Created a system restore point.
[1240:15D8][2014-08-13T12:06:10]i323: Registering package dependency provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, version: 12.2.0.36, package: Studio
[1240:15D8][2014-08-13T12:06:10]i325: Registering dependency:
{d5f0a119-9ba3-4a19-b1cf-882c39cb4720} on package provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, package: Studio
[0E6C:10D4][2014-08-13T12:06:10]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0E6C:10D4][2014-08-13T13:13:31]i500: Shutting down, exit code: 0x0
Already I have tried the work around as clean up the temp folder, restart the
machine and reinstall the setup. It also didn't work. My setup installation was
stuck in starting state itself. We don't want to follow this work around
anymore as this is not worked in our machines. Can you please provide solution
for this issue?
Thanks in Advance!
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] No progress in installation
Hi All,
We didn't deleted any stuff out of our package cache. We are facing this
installation problem in some rare machines configuration. Could anyone provide
solution to this problem? We don't want to follow the work around anymore.
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: 25 August 2014 11:23 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] No progress in installation
My best guess is that you deleted stuff out of your package cache without
updating the appropriate Add/Remove Programs registration as well.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Vadivel Natarajan [mailto:vadiv...@syncfusion.com]
Sent: Monday, August 25, 2014 10:04 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] No progress in installation
Hi,
we had created an installer using Bootstrapper and Burn with wix 3.7. In some
machines, our setup installation was not started. Setup installation was in a
starting state. No progress in installation.
We are getting the below error when we look at the log file.
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\Application_1.1.0.3.exe
[0E6C:10D4][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[0E6C:10D4][2014-08-13T12:03:59]i199: Detect complete, result: 0x0
[0E6C:10D4][2014-08-13T12:03:59]i300: Apply begin
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to get size of
pseudo bundle: C:\ProgramData\Package
Cache\{6f998459-8c96-468d-add4-c3fbae829931}\ Application_1.1.0.3.exe
[1240:15D8][2014-08-13T12:03:59]e000: Error 0x80070002: Failed to initialize
package from related bundle id: {6f998459-8c96-468d-add4-c3fbae829931}
[1240:15D8][2014-08-13T12:04:02]i360: Creating a system restore point.
[1240:15D8][2014-08-13T12:06:10]i361: Created a system restore point.
[1240:15D8][2014-08-13T12:06:10]i323: Registering package dependency provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, version: 12.2.0.36, package: Studio
[1240:15D8][2014-08-13T12:06:10]i325: Registering dependency:
{d5f0a119-9ba3-4a19-b1cf-882c39cb4720} on package provider:
{2882A35F-95A8-4C34-91E7-88433FE3116E}, package: Studio
[0E6C:10D4][2014-08-13T12:06:10]i399: Apply complete, result: 0x0, restart:
None, ba requested restart: No
[0E6C:10D4][2014-08-13T13:13:31]i500: Shutting down, exit code: 0x0
Already I have tried the work around as clean up the temp folder, restart the
machine and reinstall the setup. It also didn't work. My setup installation was
stuck in starting state itself. We don't want to follow this work around
anymore as this is not worked in our machines. Can you please provide solution
for this issue?
Thanks in Advance!
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Intermittent errors setting Windows 8 properties on shortcuts
My notes indicate that you need to set a System.AppUserModel.ID for these to
work (I did this research a while ago and don't remember the details and if it
is still accurate under windows 8.1).
I understand though that if you don't do it explicitly windows will allocate
you one on the fly, but may be worth a try.
Check out
http://msdn.microsoft.com/en-us/library/windows/desktop/dd391569(v=vs.85).aspx
to see if its relevant to your situation.
My example shortcut
Component Id=ProductShortcut
RegistryValue Root=HKMU Key=Software\company\ShortcutTest\Installer
Name=ProductShortcut Value=KeyPath KeyPath=yes Type=string /
Shortcut Id=ProductShortcut Name=The Application Description=The
application. IconIndex=0 Icon=ProductIcon.exe
Target=[#TheApplication.exe]
ShortcutProperty Key=System.AppUserModel.ID
Value=Company.TheApplication.exe /
ShortcutProperty Key={9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12 Value=1 /
!--
Name: System.AppUserModel.StartPinOption - PKEY_AppUserModel_StartPinOption
Type: UInt32 - VT_UI4
FormatID: {9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12
Note: Set this property on a shortcut to (1) prevent an application from being
automatically pinned to Start screen upon installation; or
(2) indicate that an item is programmatically added to launcher via user
action (which implies automatically pin to Start and delete on unpin).
Note: It has to be a guid to stop windows 7 throwing a warning dialogue.
see http://support.microsoft.com/kb/2745126
em Note: that you must also set System.AppUserModel.ID first or the property
will not be used. /em
--
/Shortcut
-Original Message-
From: John Hall [mailto:john.h...@cambridgetechgroup.com]
Sent: 16 September 2014 17:40
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
Rob,
I am using the GUID - it appears in the error message. I've got a define called
var.Prop_System_AppUserModel_NoPin that I use.
Regards,
John
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: 16 September 2014 16:59
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
Know Windows Installer issue. Use the GUID of the property instead of the name.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: John Hall [mailto:john.h...@cambridgetechgroup.com]
Sent: Tuesday, September 16, 2014 3:11 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
Hi,
In my installer I have a number of shortcuts installed on the Start Menu that I
don't want to appear on the Windows 8 start screen. I therefore set both the
System.AppUserModel.StartPinOption and
System.AppUserModel.ExcludeFromShowInNewInstall properties for each of these
shortcuts. My code looks like this:
?define var.Prop_System_AppUserModel_NoPin =
{9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12 ?
Component Id=index.chm Guid={17C863A4-E982-492F-9F76-6E5A09BC65E8}
File Id=index.chm Name=index.chm KeyPath=yes
Shortcut Id=Shortcut.Help
Directory=StartMenu.Help
Name=XJTAG Help
Show=normal
Advertise=no
ShortcutProperty
Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1 /
ShortcutProperty Key=$(var.Prop_System_AppUserModel_NoPin)
Value=1 /
/Shortcut
/File
RemoveFile Id=Remove.index.chw Name=index.chw On=uninstall /
/Component
Every now and then an installation on Windows 7 will display a dialog saying:
Warning 1946.Property '{9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12' for shortcut
'XJTAG Help' could not be set.
The warning ultimately seems benign, but it is not a good user experience. It
warning is not consistent or reproducible. Any ideas?
Thanks,
John
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL
Re: [WiX-users] Intermittent errors setting Windows 8 properties on shortcuts
David,
Thank you for that - I will take a look and see if that helps.
Regards,
John
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 17 September 2014 10:15
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
My notes indicate that you need to set a System.AppUserModel.ID for these to
work (I did this research a while ago and don't remember the details and if it
is still accurate under windows 8.1).
I understand though that if you don't do it explicitly windows will allocate
you one on the fly, but may be worth a try.
Check out
http://msdn.microsoft.com/en-us/library/windows/desktop/dd391569(v=vs.85).aspx
to see if its relevant to your situation.
My example shortcut
Component Id=ProductShortcut
RegistryValue Root=HKMU Key=Software\company\ShortcutTest\Installer
Name=ProductShortcut Value=KeyPath KeyPath=yes Type=string /
Shortcut Id=ProductShortcut Name=The Application Description=The
application. IconIndex=0 Icon=ProductIcon.exe
Target=[#TheApplication.exe]
ShortcutProperty Key=System.AppUserModel.ID
Value=Company.TheApplication.exe /
ShortcutProperty Key={9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12 Value=1 /
!--
Name: System.AppUserModel.StartPinOption - PKEY_AppUserModel_StartPinOption
Type: UInt32 - VT_UI4
FormatID: {9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12
Note: Set this property on a shortcut to (1) prevent an application from being
automatically pinned to Start screen upon installation; or
(2) indicate that an item is programmatically added to launcher via user
action (which implies automatically pin to Start and delete on unpin).
Note: It has to be a guid to stop windows 7 throwing a warning dialogue.
see http://support.microsoft.com/kb/2745126
em Note: that you must also set System.AppUserModel.ID first or the property
will not be used. /em
--
/Shortcut
-Original Message-
From: John Hall [mailto:john.h...@cambridgetechgroup.com]
Sent: 16 September 2014 17:40
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
Rob,
I am using the GUID - it appears in the error message. I've got a define called
var.Prop_System_AppUserModel_NoPin that I use.
Regards,
John
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: 16 September 2014 16:59
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
Know Windows Installer issue. Use the GUID of the property instead of the name.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: John Hall [mailto:john.h...@cambridgetechgroup.com]
Sent: Tuesday, September 16, 2014 3:11 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Intermittent errors setting Windows 8 properties on
shortcuts
Hi,
In my installer I have a number of shortcuts installed on the Start Menu that I
don't want to appear on the Windows 8 start screen. I therefore set both the
System.AppUserModel.StartPinOption and
System.AppUserModel.ExcludeFromShowInNewInstall properties for each of these
shortcuts. My code looks like this:
?define var.Prop_System_AppUserModel_NoPin =
{9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12 ?
Component Id=index.chm Guid={17C863A4-E982-492F-9F76-6E5A09BC65E8}
File Id=index.chm Name=index.chm KeyPath=yes
Shortcut Id=Shortcut.Help
Directory=StartMenu.Help
Name=XJTAG Help
Show=normal
Advertise=no
ShortcutProperty
Key=System.AppUserModel.ExcludeFromShowInNewInstall Value=1 /
ShortcutProperty Key=$(var.Prop_System_AppUserModel_NoPin)
Value=1 /
/Shortcut
/File
RemoveFile Id=Remove.index.chw Name=index.chw On=uninstall /
/Component
Every now and then an installation on Windows 7 will display a dialog saying:
Warning 1946.Property '{9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3}, 12' for shortcut
'XJTAG Help' could not be set.
The warning ultimately seems benign, but it is not a good user experience. It
warning is not consistent or reproducible. Any ideas?
Thanks,
John
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When
Re: [WiX-users] Check that at least one Feature is selected
Sorry, I misunderstood your question. I thought you didn't want to leave
the feature selection dialog until at least one feature was selected for
install.
Looking back at your original post, I'm still not clear what you are trying
to accomplish/solve.
On Tue, Sep 16, 2014 at 4:57 AM, Noel Farrugia noel.farru...@outlook.com
wrote:
So there isn't a simpler solution?
All I want to do is have access to a variable, in this case myFeature
from another file.
Date: Mon, 15 Sep 2014 09:21:00 -0400
From: yellowjacketl...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Check that at least one Feature is selected
I solved this same issue with a custom action on the next button of the
feature selection dialog. I tried solving it within Wix/Windows
Installer
but was unable to.
The pseudo-code is something like this...
Publish Dialog=CustomizeDlg Control=Next Event=DoAction
Value=CAMustSelectOne Order=11/Publish
Publish Dialog=CustomizeDlg Control=Next Event=NewDialog
Value=VerifyReadyDlg Order=2![CDATA[ATLEASTONESELECTED
0]]/Publish
Custom Action looked something like this (error handling and exception
management removed for brevity):
// these are all hidden or container only features,
// if they are selected for install, they are not considered a real
feature
private static readonly string[] IgnoredFeatures = { Server, Logs,
Data, WebSites, WindowsServices, Tools };
[CustomAction]
public static ActionResult MustSelectOne(Session session)
{
ActionResult installResult = ActionResult.Success;
// assume we success until told otherwise
session[ATLEASTONESELECTED] = 1;
if (NoFeaturesSelected(session))
{
session[ATLEASTONESELECTED] = 0;
MessageBox.Show(new Form() { TopMost = true }, One or more
features must be selected);
}
return installResult;
}
private static bool NoFeaturesSelected(Session session)
{
return session.Features.Where(feature =
!IgnoredFeatures.Contains(feature.Name)).All(feature =
feature.RequestState != InstallState.Local);
}
On Mon, Sep 15, 2014 at 8:55 AM, Noel Farrugia
noel.farru...@outlook.com
wrote:
I need to access MyFeature in the UserInterface code to make a
condition
such that if no feature is selected for installation the Next button
can
be disabled.
Thanks and Regards,
Noel
From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 15 Sep 2014 12:24:04 +
Subject: Re: [WiX-users] Check that at least one Feature is selected
Currently, there is limited scoping of properties in Wix 3.x. The
only
problem you may sometimes run into is when a property crosses the UI to
Execute boundary--to do that, you'll need a public secure property.
So, how exactly do you want to access MyFeature?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |
jocoo...@jackhenry.com
-Original Message-
From: Noel Farrugia [mailto:noel.farru...@outlook.com]
Sent: Monday, September 15, 2014 7:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Check that at least one Feature is selected
Hi all,
I have a setup with feature selection enabled like this one now, in a
file called MyInstaller.wxs,
Feature Id=MyFeature
Title=MyTitle
Description=Desc
Level=1 AllowAdvertise=no Absent=allow
TypicalDefault=install
ComponentGroupRef Id=Test Component/
.
.
.
/Feature
The code that handles the User interface is in another file called
UserInterface.wxi.
I know that to check if a certain feature is selected I need to do
[CDATA[MyFeature=3]] in the Publish line example:
Publish Property=FeatureChoiceDlgPrev
Value=InstallWelcomeDlg$(var.allowFeatureChoice) = 1/Publish
now my question is how can I access the MyFeature which is located
in
MyInstaller.wxs in the UserInterface.wxifile ?
Thanks a lot for your help :)
Noel
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/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
Re: [WiX-users] Installing VSTO as pre-requisites from Bundle.wxs Failed
Hi Licha,
Thanks for the reply. Can you please let me know how can I get the permanent
link?
Regards,
Chetan.
-Original Message-
From: Liz [mailto:chang@gmail.com]
Sent: Wednesday, September 17, 2014 3:57 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Installing VSTO as pre-requisites from Bundle.wxs
Failed
The VSTO redist package you downloaded via the fwlink is failing signature
verification because it was updated last week, which most likely no longer
matches with the vstor_redist.exe you used to compile your bootstrapper.
Updating the redist source file to the latest version should resolve this
issue. And you might want to consider using a permanent link going forward.
On Mon, Sep 15, 2014 at 4:08 AM, Chetan Rajakumar
chetan_rajaku...@infosys.com wrote:
Hi,Hi,
I've created a WIX (v3.7.0.0) installer for our VSTO application on
Win 7
64 bit machine. Which do custom installation successfully. And I've
also create Bundle.wxs file for installing the prerequisites for VSTO,
like .Net Framework 4.0 client profile and VSTO 4.0. runtime.
When I run our exe file it search for VSTO and start download VSTO
from http://go.microsoft.com/fwlink/?LinkId=158917. but gives the
below error
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to find
expected public key in certificate chain.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
verify expected payload against actual certificate chain.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
verify signature of payload: VSTORuntime
[0BE8:06F0][2013-08-06T10:49:18]e310: Failed to verify payload:
VSTORuntime at path: C:\ProgramData\Package
Cache\.unverified\VSTORuntime,
error: 0x80070490. Deleting file.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
cache
payload: VSTORuntime
[15CC:0568][2013-08-06T10:49:18]e314: Failed to cache payload:
VSTORuntime from working path:
C:\Users\UA17C9~1.JAI\AppData\Local\Temp\{f3bea074-7c76-4831-b8ed-2202
1127ba0d}\VSTORuntime,
error: 0x80070490.
[15CC:0568][2013-08-06T10:49:18]e349: Application requested retry of
payload: VSTORuntime, encountered error: 0x80070490. Retrying...
Installer do above same step for 3 times and then finally show error
message and stop the installation.
Don't know why this is happening. And we need to install VSTO 4.0
Runtime automatically. When I run vstor_redist.exe manually, it runs
successfully.
* Code is as below:
Bundle.wxs
Bundle Name=$(var.ProductName) Version=$(var.ProductVersion)
Manufacturer=$(var.Manufacturer) UpgradeCode=$(var.UpgradeCode)
IconSourceFile=$(var.ResourceFiles)\Icon.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication
LogoFile=$(var.ResourceFiles)\BootStrap Logo.bmp SuppressOptionsUI=yes
LicenseFile=Confidential.rtf /
/BootstrapperApplicationRef
util:RegistrySearch Id=VSTORuntimeVersionV4 Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4\ Value=Version
Variable=VSTORVersionV4/
util:RegistrySearch Id=VSTORuntimeVersionV4M Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4M\
Value=VSTORFeature_CLR40 Variable=VSTORFeature/
util:RegistrySearch Id=VSTORuntimeVersionV4R Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4R\
Value=Version Variable=VSTORVersionV4R/
util:RegistrySearch Id=DotNetTest Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Client Value=Install
Variable=DotNetInstall/
util:RegistrySearch Id=DotNetVersion Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Client Value=Version
Variable=DotNetVersion/
Chain
ExePackage Id=dotNetFx40_Client_x86_x64
SourceFile=$(var.PreReqPath)\DotNetFX40Client\dotNetFx40_Client_x86_x64.exe
PerMachine=yes Cache=no
Compressed=no
DownloadUrl=
http://download.microsoft.com/download/7/B/6/7B629E05-399A-4A92-B5BC-4
84C74B5124B/dotNetFx40_Client_setup.exe
Permanent=yes
InstallCommand=/q /norestart
DetectCondition=NOT DotNetInstall
InstallCondition=NOT
DotNetInstall OR NOT (DotNetVersion =v4.0.30319) /
ExePackage Id=VSTORuntime
SourceFile=$(var.PreReqPath)\VSTOR40\vstor_redist.exe Permanent=yes
Vital=yes Cache=no Compressed=no
DownloadUrl=
http://go.microsoft.com/fwlink/?LinkId=158917;
PerMachine=yes
InstallCommand=/q /norestart
[WiX-users] Multiple Instance and Product Code
Hi All, The product requirement at my work changed. We're being asked to support multiple instances of the same product. I've read fromthe forum that InstanceTransform is the way to go and that requires different Product Code for each instance. I've used Product Id=* to auto-gen product id. How do generate a Product Id GUID manually? Can someone please help? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-Instance-and-Product-Code-tp7596863.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple Instance and Product Code
You populate an InstanceTransforms element with Instance elements. The InstanceTransforms element as a Property Attribute which you'll want to have a public property that will key into each of the Instance@Id attributes. Each Instance element, in addition to an ID, also has a ProductCode attribute which is where you provide the GUID for each instances' ProductCode. There is also a ProductName attribute where you provide the ProductName for each instance. The table is currently static, which means you'll need to have enough Instance elements to cover your max case. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Wednesday, September 17, 2014 10:21 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Multiple Instance and Product Code Hi All, The product requirement at my work changed. We're being asked to support multiple instances of the same product. I've read fromthe forum that InstanceTransform is the way to go and that requires different Product Code for each instance. I've used Product Id=* to auto-gen product id. How do generate a Product Id GUID manually? Can someone please help? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-Instance-and-Product-Code-tp7596863.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/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. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issue with installer in windows 2012 server
We also target 2012R2 with Burn setups and the message System restore disabled, system restore point not created. is common in successful logs with no other failures. I notice that you have posted this message multiple times. Maybe you could collect more details or post a complete failure log. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issue-with-installer-in-windows-2012-server-tp7596756p7596866.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Greetings, I have a custom C# bootstrapper application that chains a few MSI's together and installs them. No problems here. However, we plan on introducing other add-ons to our software which are not included in our original bootstrapper app chain. These other add-ons will be MSI's (developed by other groups within the company on their own release schedule). Some of these add-ons may be available at the same time we release our main BA. What we would like to do is: * During the installation of our BA we present the user with a screen that allows them to browse for additional add-ons. * These add-ons will be installed through the BA * On uninstall, the original BA chain AND the add-ons should all be removed. What would be the best way to approach this situation? Regards, Robert Ortega -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Related bundles. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: robert_ort...@agilent.com [mailto:robert_ort...@agilent.com] Sent: Wednesday, September 17, 2014 10:44 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Greetings, I have a custom C# bootstrapper application that chains a few MSI's together and installs them. No problems here. However, we plan on introducing other add-ons to our software which are not included in our original bootstrapper app chain. These other add-ons will be MSI's (developed by other groups within the company on their own release schedule). Some of these add-ons may be available at the same time we release our main BA. What we would like to do is: * During the installation of our BA we present the user with a screen that allows them to browse for additional add-ons. * These add-ons will be installed through the BA * On uninstall, the original BA chain AND the add-ons should all be removed. What would be the best way to approach this situation? Regards, Robert Ortega -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple Instance and Product Code
Thanks for your reply John! Just to clarify, I would create an
InstanceTransform that looks like follows:
instancetransforms property=ANY_PROPERTY
instance id=InstanceId1
productcode={42A33A91-36B0-4700-A6F5-1289D22F358C}/
instance id=InstanceId2
productcode={68C62C01-D064-4CF0-9239-F5D2FF36BD9A}/
...
/instancetransforms
My question is does the productCode correspond to the Product Id=?
And how is the productCode generated?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-Instance-and-Product-Code-tp7596863p7596869.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple Instance and Product Code
1) Yes, the ProductCode attribute corresponds directly to the ProductCode for
the particular installed instance.
2) The Product Codes are static. You can generate them using Perl or with the
tool included with Visual Studio.
3) I would recommend that you set the ProductName attribute for each instance
as it isn't a pleasant user experience to try to figure out which of 16
identically named instances you want to delete.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: newuser2014 [mailto:wamplersovere...@gmail.com]
Sent: Wednesday, September 17, 2014 1:03 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Multiple Instance and Product Code
Thanks for your reply John! Just to clarify, I would create an
InstanceTransform that looks like follows:
instancetransforms property=ANY_PROPERTY
instance id=InstanceId1
productcode={42A33A91-36B0-4700-A6F5-1289D22F358C}/
instance id=InstanceId2
productcode={68C62C01-D064-4CF0-9239-F5D2FF36BD9A}/
...
/instancetransforms
My question is does the productCode correspond to the Product Id=?
And how is the productCode generated?
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-Instance-and-Product-Code-tp7596863p7596869.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/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.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing VSTO as pre-requisites from Bundle.wxs Failed
This is the fwlink that always points to the latest VSTO 2010 download page:
http://go.microsoft.com/fwlink/?LinkId=140384
After you click Download and lands on the page after, you can find the
direct download link at If your download does not start after 30 seconds,
Click here
On Wed, Sep 17, 2014 at 5:02 AM, Chetan Rajakumar
chetan_rajaku...@infosys.com wrote:
Hi Licha,
Thanks for the reply. Can you please let me know how can I get the
permanent link?
Regards,
Chetan.
-Original Message-
From: Liz [mailto:chang@gmail.com]
Sent: Wednesday, September 17, 2014 3:57 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Installing VSTO as pre-requisites from Bundle.wxs
Failed
The VSTO redist package you downloaded via the fwlink is failing signature
verification because it was updated last week, which most likely no longer
matches with the vstor_redist.exe you used to compile your bootstrapper.
Updating the redist source file to the latest version should resolve this
issue. And you might want to consider using a permanent link going forward.
On Mon, Sep 15, 2014 at 4:08 AM, Chetan Rajakumar
chetan_rajaku...@infosys.com wrote:
Hi,Hi,
I've created a WIX (v3.7.0.0) installer for our VSTO application on
Win 7
64 bit machine. Which do custom installation successfully. And I've
also create Bundle.wxs file for installing the prerequisites for VSTO,
like .Net Framework 4.0 client profile and VSTO 4.0. runtime.
When I run our exe file it search for VSTO and start download VSTO
from http://go.microsoft.com/fwlink/?LinkId=158917. but gives the
below error
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to find
expected public key in certificate chain.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
verify expected payload against actual certificate chain.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
verify signature of payload: VSTORuntime
[0BE8:06F0][2013-08-06T10:49:18]e310: Failed to verify payload:
VSTORuntime at path: C:\ProgramData\Package
Cache\.unverified\VSTORuntime,
error: 0x80070490. Deleting file.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
cache
payload: VSTORuntime
[15CC:0568][2013-08-06T10:49:18]e314: Failed to cache payload:
VSTORuntime from working path:
C:\Users\UA17C9~1.JAI\AppData\Local\Temp\{f3bea074-7c76-4831-b8ed-2202
1127ba0d}\VSTORuntime,
error: 0x80070490.
[15CC:0568][2013-08-06T10:49:18]e349: Application requested retry of
payload: VSTORuntime, encountered error: 0x80070490. Retrying...
Installer do above same step for 3 times and then finally show error
message and stop the installation.
Don't know why this is happening. And we need to install VSTO 4.0
Runtime automatically. When I run vstor_redist.exe manually, it runs
successfully.
* Code is as below:
Bundle.wxs
Bundle Name=$(var.ProductName) Version=$(var.ProductVersion)
Manufacturer=$(var.Manufacturer) UpgradeCode=$(var.UpgradeCode)
IconSourceFile=$(var.ResourceFiles)\Icon.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication
LogoFile=$(var.ResourceFiles)\BootStrap Logo.bmp
SuppressOptionsUI=yes
LicenseFile=Confidential.rtf /
/BootstrapperApplicationRef
util:RegistrySearch Id=VSTORuntimeVersionV4 Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4\
Value=Version
Variable=VSTORVersionV4/
util:RegistrySearch Id=VSTORuntimeVersionV4M Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4M\
Value=VSTORFeature_CLR40 Variable=VSTORFeature/
util:RegistrySearch Id=VSTORuntimeVersionV4R Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4R\
Value=Version Variable=VSTORVersionV4R/
util:RegistrySearch Id=DotNetTest Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Client
Value=Install
Variable=DotNetInstall/
util:RegistrySearch Id=DotNetVersion Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Client
Value=Version
Variable=DotNetVersion/
Chain
ExePackage Id=dotNetFx40_Client_x86_x64
SourceFile=$(var.PreReqPath)\DotNetFX40Client\dotNetFx40_Client_x86_x64.exe
PerMachine=yes Cache=no
Compressed=no
DownloadUrl=
http://download.microsoft.com/download/7/B/6/7B629E05-399A-4A92-B5BC-4
84C74B5124B/dotNetFx40_Client_setup.exe
Permanent=yes
InstallCommand=/q /norestart
DetectCondition=NOT DotNetInstall
InstallCondition=NOT
DotNetInstall OR NOT
[WiX-users] XMLConfig updates only from command line
Hello, I have an installer that writes default property values to an XML config file every time the installer runs . I have a new requirement that does not allow me to hardcode/set those default property values within the installer but just install the config file and only update the config file when a command line parameter is passed to update a specific value in the config file. So in other words, install the file with it's default values when harvested and *only* write/update values to it when a command line parameter is passed during installation. Is this possible? Thank you in advance, J -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Is this still possible even if I do not know what add-ons will be available at the time of my main BA release? It is so difficult finding examples of relatedbundle addons in the archives... Robert -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Wednesday, September 17, 2014 10:55 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Related bundles. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: robert_ort...@agilent.com [mailto:robert_ort...@agilent.com] Sent: Wednesday, September 17, 2014 10:44 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Greetings, I have a custom C# bootstrapper application that chains a few MSI's together and installs them. No problems here. However, we plan on introducing other add-ons to our software which are not included in our original bootstrapper app chain. These other add-ons will be MSI's (developed by other groups within the company on their own release schedule). Some of these add-ons may be available at the same time we release our main BA. What we would like to do is: * During the installation of our BA we present the user with a screen that allows them to browse for additional add-ons. * These add-ons will be installed through the BA * On uninstall, the original BA chain AND the add-ons should all be removed. What would be the best way to approach this situation? Regards, Robert Ortega -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
I am not an expert and am still learning this topic, but I think it boils
down to:
In the main bundle preemptively add a line like:
RelatedBundle Action='Detect' Id='{GUID to be shared with future related
bundles}' /
In the future add-on, update, or patch, (as indicated) add this to tell it
that it is related to the main product.
RelatedBundle Action='Addon' Id='{GUID in Main bundle ReleatedBundle
elements}' /
I also set Bundle/@Tag to a unique string in each bundle.
I have done limited testing of this approach but it seemed to work so far.
I am interesting in learning it this approach is wrong or incomplete.
There is also info here about code in an mba
http://stackoverflow.com/questions/21612377/schedule-relatedbundle-action-before-primary-bundle
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596874.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config
Greetings, I'm currently writing my own Bootstrapper Application with WPF and .NET 4.5. Because all applications installed with the BA will be run using .NET 4.5, I want set this as the supportedFramework. Unfortunately, this does not work and only opens the Prereq-Installer instead of my custom BA UX. This works: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 / /startup wix.bootstrapper host assemblyName=Company.Product.Installer supportedFramework version=v4\Full / supportedFramework version=v4\Client / /host /wix.bootstrapper This does not: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.5 / /startup wix.bootstrapper host assemblyName=MyHorizon.ImmoCRM.Installer supportedFramework version=v4.5\Client / /host /wix.bootstrapper Why? Maybe it's just supposed to work with v4.0 as the supportedRuntime, because 4.5 is an in-place upgrade. But better safe than sorry. Thanks! -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Ensure a Windows Feature is enabled?
What feature? Did you try looking in the registry? On Fri, Sep 12, 2014 at 6:15 AM, neslekkim asbj...@neslekkim.net wrote: Ensuring that it's there should not be the same as you install it :) Anyway, I need to detect if this feature is installed, so i can abort the install if it's missing, It's easy to detect IIS and .net, but is there any examples on how to do this feature checking? Is WMI really the way to do it?, was hoping that i didn't need to create an custom action.. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-a-Windows-Feature-is-enabled-tp6287035p7596779.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config
Starting with .NET 4.5, there is no client profile. On Wed, Sep 17, 2014 at 2:40 PM, Yari Serve se...@my-horizon.de wrote: Greetings, I'm currently writing my own Bootstrapper Application with WPF and .NET 4.5. Because all applications installed with the BA will be run using .NET 4.5, I want set this as the supportedFramework. Unfortunately, this does not work and only opens the Prereq-Installer instead of my custom BA UX. This works: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 / /startup wix.bootstrapper host assemblyName=Company.Product.Installer supportedFramework version=v4\Full / supportedFramework version=v4\Client / /host /wix.bootstrapper This does not: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.5 / /startup wix.bootstrapper host assemblyName=MyHorizon.ImmoCRM.Installer supportedFramework version=v4.5\Client / /host /wix.bootstrapper Why? Maybe it's just supposed to work with v4.0 as the supportedRuntime, because 4.5 is an in-place upgrade. But better safe than sorry. Thanks! -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config
Sean, Even this does not work: supportedFramework version=v4.5 / Still opening the PreReq BA instead of my custom BA. -Original Message- From: Sean Hall [mailto:r.sean.h...@gmail.com] Sent: Mittwoch, 17. September 2014 22:51 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config Starting with .NET 4.5, there is no client profile. On Wed, Sep 17, 2014 at 2:40 PM, Yari Serve se...@my-horizon.de wrote: Greetings, I'm currently writing my own Bootstrapper Application with WPF and .NET 4.5. Because all applications installed with the BA will be run using .NET 4.5, I want set this as the supportedFramework. Unfortunately, this does not work and only opens the Prereq-Installer instead of my custom BA UX. This works: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 / /startup wix.bootstrapper host assemblyName=Company.Product.Installer supportedFramework version=v4\Full / supportedFramework version=v4\Client / /host /wix.bootstrapper This does not: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.5 / /startup wix.bootstrapper host assemblyName=Company.Product.Installer supportedFramework version=v4.5\Client / /host /wix.bootstrapper Why? Maybe it's just supposed to work with v4.0 as the supportedRuntime, because 4.5 is an in-place upgrade. But better safe than sorry. Thanks! -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg. clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Thanks Phil. However I'm still not clear about the entire workflow. I only
have one bootstrapper application which includes no addons. Addons will come
later as separate MSI's (on their own physical DVD to make things more
interesting). So on the DVD I'll literally have just one MSI and maybe a text
file readme of some sort.
How do I make the connection between:
RelatedBundle Action='Detect' Id='{GUID to be shared with future related
bundles}' / /**I understand that this is defined in my bootstrapper app**/
And
Addon1.msi (again, this MSI is delivered on a different media and knows nothing
about my bootstrapper app)?
Our initial idea was to have one of our UI screens in our BA prompt for the
media, find the MSI, and install it.
Hope that makes sense..
Regards,
Robert
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Wednesday, September 17, 2014 1:24 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper
Application Bundle
I am not an expert and am still learning this topic, but I think it boils down
to:
In the main bundle preemptively add a line like:
RelatedBundle Action='Detect' Id='{GUID to be shared with future related
bundles}' /
In the future add-on, update, or patch, (as indicated) add this to tell it that
it is related to the main product.
RelatedBundle Action='Addon' Id='{GUID in Main bundle ReleatedBundle
elements}' /
I also set Bundle/@Tag to a unique string in each bundle.
I have done limited testing of this approach but it seemed to work so far.
I am interesting in learning it this approach is wrong or incomplete.
There is also info here about code in an mba
http://stackoverflow.com/questions/21612377/schedule-relatedbundle-action-before-primary-bundle
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596874.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] XMLConfig updates only from command line
Also the command line parameters do update the config file. Just wanted to be clear that the XML config file should only be written to when a command line parameter is used. Thanks again for any assistance. J On Wed, Sep 17, 2014 at 2:17 PM, Jeremiahf jeremi...@gmail.com wrote: Hello, I have an installer that writes default property values to an XML config file every time the installer runs . I have a new requirement that does not allow me to hardcode/set those default property values within the installer but just install the config file and only update the config file when a command line parameter is passed to update a specific value in the config file. So in other words, install the file with it's default values when harvested and *only* write/update values to it when a command line parameter is passed during installation. Is this possible? Thank you in advance, J -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config
It's impossible to tell what's wrong without looking at the log in the %TEMP% directory. On Wed, Sep 17, 2014 at 4:02 PM, Yari Serve se...@my-horizon.de wrote: Sean, Even this does not work: supportedFramework version=v4.5 / Still opening the PreReq BA instead of my custom BA. -Original Message- From: Sean Hall [mailto:r.sean.h...@gmail.com] Sent: Mittwoch, 17. September 2014 22:51 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config Starting with .NET 4.5, there is no client profile. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and supportedFramework in BootstrapperCore.config
I believe the following line is the interesting one:
[1E2C:0F98][2014-09-17T23:23:07]i000: Loading prerequisite bootstrapper
application because managed host could not be loaded, error: 0x80070490.
For the sake of completion, here's the log:
[1E2C:0F98][2014-09-17T23:23:07]i001: Burn v3.8.1128.0, Windows v6.3 (Build
9600: Service Pack 0), path:
D:\Development\Company\Source\Product\Main\Installer\Company.Product.Install
er.Bootstrapper\bin\Debug\Company Product Installer.exe, cmdline: ''
[1E2C:0F98][2014-09-17T23:23:07]i000: Setting string variable 'WixBundleLog'
to value 'C:\Users\User1\AppData\Local\Temp\Company
Product_2015_20140917232307.log'
[1E2C:0F98][2014-09-17T23:23:07]i000: Setting string variable
'WixBundleOriginalSource' to value
'D:\Development\Company\Source\Product\Main\Installer\Company.Product.Instal
ler.Bootstrapper\bin\Debug\Company Product Installer.exe'
[1E2C:0F98][2014-09-17T23:23:07]i000: Setting string variable
'WixBundleName' to value 'Company Product 2015'
[1E2C:0F98][2014-09-17T23:23:07]i000: Loading prerequisite bootstrapper
application because managed host could not be loaded, error: 0x80070490.
[1E2C:0F98][2014-09-17T23:23:07]i100: Detect begin, 2 packages
[1E2C:0F98][2014-09-17T23:23:07]i000: Setting string variable
'NETFRAMEWORK45' to value '378675'
[1E2C:0F98][2014-09-17T23:23:07]i052: Condition 'NETFRAMEWORK45 = 378389'
evaluates to true.
[1E2C:0F98][2014-09-17T23:23:07]i101: Detected package: NetFx45Web, state:
Present, cached: None
[1E2C:0F98][2014-09-17T23:23:07]i101: Detected package:
ProductClientPackage, state: Absent, cached: None
[1E2C:0F98][2014-09-17T23:23:07]i199: Detect complete, result: 0x0
[1E2C:0F98][2014-09-17T23:23:09]i500: Shutting down, exit code: 0x642
[1E2C:0F98][2014-09-17T23:23:09]i000: The prerequisites were already
installed. The bootstrapper application will not be reloaded to prevent an
infinite loop.
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: NETFRAMEWORK45 = 378675
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleAction = 4
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleElevated = 0
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleInstalled = 0
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleLog =
C:\Users\User1\AppData\Local\Temp\Company Product_2015_20140917232307.log
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleManufacturer =
Company
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleName = Company
Product 2015
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleOriginalSource =
D:\Development\Company\Source\Product\Main\Installer\Company.Product.Install
er.Bootstrapper\bin\Debug\Company Product Installer.exe
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleProviderKey =
{1525682b-1b58-43a7-8166-ab90295e099f}
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleTag =
[1E2C:0F98][2014-09-17T23:23:09]i410: Variable: WixBundleVersion = 14.1.0.0
[1E2C:0F98][2014-09-17T23:23:09]i007: Exit code: 0x642, restarting: No
-Original Message-
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: Mittwoch, 17. September 2014 23:19
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and
supportedFramework in BootstrapperCore.config
It's impossible to tell what's wrong without looking at the log in the
%TEMP% directory.
On Wed, Sep 17, 2014 at 4:02 PM, Yari Serve se...@my-horizon.de wrote:
Sean,
Even this does not work:
supportedFramework version=v4.5 /
Still opening the PreReq BA instead of my custom BA.
-Original Message-
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: Mittwoch, 17. September 2014 22:51
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] .NET FX 4.5 as the supportedRuntime and
supportedFramework in BootstrapperCore.config
Starting with .NET 4.5, there is no client profile.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Rob's advice was to use a Related Bundle , which would involve creating a bundle.exe for each addon, and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596883.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Thanks Phil - that tiny piece of information looks to have cleared up most of my confusion. Thanks! -Robert -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Wednesday, September 17, 2014 2:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Rob's advice was to use a Related Bundle , which would involve creating a bundle.exe for each addon, and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-MSI-s-NOT-Included-in-my-Bootstrapper-Application-Bundle-tp7596867p7596883.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle
Could ship a newer bundle that knows about new MSIs and use bundle updates. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Wednesday, September 17, 2014 2:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing MSI's NOT Included in my Bootstrapper Application Bundle Rob's advice was to use a Related Bundle , which would involve creating a bundle.exe for each addon, and using the RelatedBundle element in each Bundle to establish the relationships. If you use 'Related Bundles' Burn does a lot of work for you tracking not only the install but the uninstall process. This is a Burn concept and MSI is not going to know about it. I don't know how you would implement your plan. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] CustomAction to execute batch file causes uninstall to fail
Hi, I have a custom action during the installation process to execute a batch file to replace some config file. CustomAction Id=BatchScript Directory=AV Execute=deferred Impersonate=yes Return=check ExeCommand=[SystemFolder]\cmd /c quot;ConfigBatch.batquot; / InstallExecuteSequence ... Custom Action=BatchScript After=InstallFiles / /InstallExecuteSequence The installation goes smoothly. However, uninstallation fails. Do you know what might be the issue and a potential fix for this problem? Thank you very much in advance! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-to-execute-batch-file-causes-uninstall-to-fail-tp7596886.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction to execute batch file causes uninstall to fail
You're referring to it as an install custom action, but I see no condition that causes it to be called only on install. In other words it's also being called at uninstall time and failing. --- Phil Wilson On Wed, Sep 17, 2014 at 4:08 PM, newuser2014 wamplersovere...@gmail.com wrote: Hi, I have a custom action during the installation process to execute a batch file to replace some config file. CustomAction Id=BatchScript Directory=AV Execute=deferred Impersonate=yes Return=check ExeCommand=[SystemFolder]\cmd /c quot;ConfigBatch.batquot; / InstallExecuteSequence ... Custom Action=BatchScript After=InstallFiles / /InstallExecuteSequence The installation goes smoothly. However, uninstallation fails. Do you know what might be the issue and a potential fix for this problem? Thank you very much in advance! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-to-execute-batch-file-causes-uninstall-to-fail-tp7596886.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction to execute batch file causes uninstall to fail
Phil is right. Just add this to the custom action sequence: Custom Action=BatchScript After=InstallFiles ![CDATA[ REMOVEALL]]/Custom -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Wednesday, September 17, 2014 4:16 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] CustomAction to execute batch file causes uninstall to fail You're referring to it as an install custom action, but I see no condition that causes it to be called only on install. In other words it's also being called at uninstall time and failing. --- Phil Wilson On Wed, Sep 17, 2014 at 4:08 PM, newuser2014 wamplersovere...@gmail.com wrote: Hi, I have a custom action during the installation process to execute a batch file to replace some config file. CustomAction Id=BatchScript Directory=AV Execute=deferred Impersonate=yes Return=check ExeCommand=[SystemFolder]\cmd /c quot;ConfigBatch.batquot; / InstallExecuteSequence ... Custom Action=BatchScript After=InstallFiles / /InstallExecuteSequence The installation goes smoothly. However, uninstallation fails. Do you know what might be the issue and a potential fix for this problem? Thank you very much in advance! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAc tion-to-execute-batch-file-causes-uninstall-to-fail-tp7596886.html Sent from the wix-users mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg. clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction to execute batch file causes uninstall to fail
Or better, associate with a Component's state. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Pavan Konduru [mailto:pavan.kond...@accelrys.com] Sent: Wednesday, September 17, 2014 5:13 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] CustomAction to execute batch file causes uninstall to fail Phil is right. Just add this to the custom action sequence: Custom Action=BatchScript After=InstallFiles ![CDATA[ REMOVEALL]]/Custom -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] XMLConfig updates only from command line
Hi J, Yes this is possible. Are you using just an MSI or do you use a burn bootstrapper? In case of an MSI you can define a property that you pass on the command line, similar to INSTALLDIR=... You can create your own property say UPDATEXML=value where value can be yes or no so something like that. In your component that executes the xml update (or your custom action) you can use the 'condition' facility to let it run based on your command line supplied value. For custom actions you can use the format: custom action ..UPDATEXML=yes/custom For components you can use the condition tag: condition![CDATA[UPDATEXML=yes]]/condition But check the documentation for exact syntax. Best regards, Rob van Rosmalen B ICT software engineer stabiplan +31 172 65 02 65 www.stabiplan.nl www.stabiplan.nl/disclaimer -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: woensdag 17 september 2014 23:14 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] XMLConfig updates only from command line Also the command line parameters do update the config file. Just wanted to be clear that the XML config file should only be written to when a command line parameter is used. Thanks again for any assistance. J On Wed, Sep 17, 2014 at 2:17 PM, Jeremiahf jeremi...@gmail.com wrote: Hello, I have an installer that writes default property values to an XML config file every time the installer runs . I have a new requirement that does not allow me to hardcode/set those default property values within the installer but just install the config file and only update the config file when a command line parameter is passed to update a specific value in the config file. So in other words, install the file with it's default values when harvested and *only* write/update values to it when a command line parameter is passed during installation. Is this possible? Thank you in advance, J -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing VSTO as pre-requisites from Bundle.wxs Failed
Thank you very much Licha.
-Original Message-
From: Liz [mailto:chang@gmail.com]
Sent: Wednesday, September 17, 2014 11:57 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Installing VSTO as pre-requisites from Bundle.wxs
Failed
This is the fwlink that always points to the latest VSTO 2010 download page:
http://go.microsoft.com/fwlink/?LinkId=140384
After you click Download and lands on the page after, you can find the direct
download link at If your download does not start after 30 seconds, Click here
On Wed, Sep 17, 2014 at 5:02 AM, Chetan Rajakumar
chetan_rajaku...@infosys.com wrote:
Hi Licha,
Thanks for the reply. Can you please let me know how can I get the
permanent link?
Regards,
Chetan.
-Original Message-
From: Liz [mailto:chang@gmail.com]
Sent: Wednesday, September 17, 2014 3:57 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Installing VSTO as pre-requisites from
Bundle.wxs Failed
The VSTO redist package you downloaded via the fwlink is failing
signature verification because it was updated last week, which most
likely no longer matches with the vstor_redist.exe you used to compile your
bootstrapper.
Updating the redist source file to the latest version should resolve
this issue. And you might want to consider using a permanent link going
forward.
On Mon, Sep 15, 2014 at 4:08 AM, Chetan Rajakumar
chetan_rajaku...@infosys.com wrote:
Hi,Hi,
I've created a WIX (v3.7.0.0) installer for our VSTO application on
Win 7
64 bit machine. Which do custom installation successfully. And I've
also create Bundle.wxs file for installing the prerequisites for
VSTO, like .Net Framework 4.0 client profile and VSTO 4.0. runtime.
When I run our exe file it search for VSTO and start download VSTO
from http://go.microsoft.com/fwlink/?LinkId=158917. but gives the
below error
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
find expected public key in certificate chain.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
verify expected payload against actual certificate chain.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
verify signature of payload: VSTORuntime
[0BE8:06F0][2013-08-06T10:49:18]e310: Failed to verify payload:
VSTORuntime at path: C:\ProgramData\Package
Cache\.unverified\VSTORuntime,
error: 0x80070490. Deleting file.
[0BE8:06F0][2013-08-06T10:49:18]e000: Error 0x80070490: Failed to
cache
payload: VSTORuntime
[15CC:0568][2013-08-06T10:49:18]e314: Failed to cache payload:
VSTORuntime from working path:
C:\Users\UA17C9~1.JAI\AppData\Local\Temp\{f3bea074-7c76-4831-b8ed-22
02
1127ba0d}\VSTORuntime,
error: 0x80070490.
[15CC:0568][2013-08-06T10:49:18]e349: Application requested retry of
payload: VSTORuntime, encountered error: 0x80070490. Retrying...
Installer do above same step for 3 times and then finally show error
message and stop the installation.
Don't know why this is happening. And we need to install VSTO 4.0
Runtime automatically. When I run vstor_redist.exe manually, it
runs
successfully.
* Code is as below:
Bundle.wxs
Bundle Name=$(var.ProductName) Version=$(var.ProductVersion)
Manufacturer=$(var.Manufacturer) UpgradeCode=$(var.UpgradeCode)
IconSourceFile=$(var.ResourceFiles)\Icon.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication
LogoFile=$(var.ResourceFiles)\BootStrap Logo.bmp
SuppressOptionsUI=yes
LicenseFile=Confidential.rtf /
/BootstrapperApplicationRef
util:RegistrySearch Id=VSTORuntimeVersionV4 Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4\
Value=Version
Variable=VSTORVersionV4/
util:RegistrySearch Id=VSTORuntimeVersionV4M Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4M\
Value=VSTORFeature_CLR40 Variable=VSTORFeature/
util:RegistrySearch Id=VSTORuntimeVersionV4R Root=HKLM
Key=SOFTWARE\Wow6432Node\Microsoft\VSTO Runtime Setup\v4R\
Value=Version Variable=VSTORVersionV4R/
util:RegistrySearch Id=DotNetTest Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Client
Value=Install
Variable=DotNetInstall/
util:RegistrySearch Id=DotNetVersion Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Client
Value=Version
Variable=DotNetVersion/
Chain
ExePackage Id=dotNetFx40_Client_x86_x64
SourceFile=$(var.PreReqPath)\DotNetFX40Client\dotNetFx40_Client_x86_x64.exe
PerMachine=yes Cache=no
Compressed=no
DownloadUrl=
http://download.microsoft.com/download/7/B/6/7B629E05-399A-4A92-B5BC
-4
