Need step by step directions to activate burn bootstrape
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development
To help avoid prompts for source in patch-on-patch scenarios Windows
Installer has been known to cache originals of files that are patched, but
that behavior can be turned off. Maybe it is off for uncompressed sources?
Date: Wed, 8 Jan 2014 13:40:48 -0800
From: dtkob...@gmail.com
To:
Please tell us how we can improve this:
http://wixtoolset.org/documentation/manual/v3/bundle/
Date: Thu, 9 Jan 2014 00:04:47 -0800
From: jessro...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Activation of burn step by step
Need step by step directions to activate
Good morning Wix users :)
I've come across an instance where uninstalling our product while it is running
succeeds and leaves the application running. The Program Files directory, ARP
entry, all registry keys etc are all removed. Going into task manager, right
clicking the application and
Depends on the file locks. A binary that is simply loaded in a process can be
moved/renamed and the directory it was originally in when it was loaded removed
without disturbing the process, but if the process is holding other files in
that same directory open with different kinds of file locks
Interesting, thank you for that prompt reply.
Is there a setting to modify this behaviour? Or am I going to have to modify
our product?
To clarify, I do not want to be able to uninstall with the application running.
Simon
-Original Message-
From: Blair Murri [mailto:os...@live.com]
I have the following components that get installed:
!-- Identify ComponentGroups to be installed --
Feature Id=ProductFeature Title=HRActions Setup Level=1
ConfigurableDirectory=INSTALL_FOLDER
ComponentGroupRef Id=BinComponents /
ComponentGroupRef Id=ConfigComponents /
I am converting a install project from an older Windows Installer to WiX.
This project sets up a website and associated application pool with the
following parameters (used in conjunction with the
System.Configuration.Install.Installer class):
appPools
appPool name=HRActionsAppPool !--
This will get you started:
http://www.codeproject.com/Articles/115036/Creating-WIX-Installer-for-ASP-NET-Web-Application
Carter
Quoting Brian Enderle bria...@gmail.com:
I am converting a install project from an older Windows Installer to WiX.
This project sets up a website and associated
Thanks, I actually followed this article to create a working installer but
my specific issue is setting all the values that the old installer did
(StartupTimeLimit, ConnectionTimeout, AspScriptTimeOut, DefaultDoc, etc.).
Brian
If you can't explain it simply, you don't understand it well enough.
Check out Link [7] at the bottom...
Quoting Brian Enderle bria...@gmail.com:
Thanks, I actually followed this article to create a working installer but
my specific issue is setting all the values that the old installer did
(StartupTimeLimit, ConnectionTimeout, AspScriptTimeOut, DefaultDoc,
There are feature requests open to configure more of IIS. It is likely your
settings are in that list. All that is needed is for some people to step up and
help implement that changes.
-Original Message-
From: Carter Young [mailto:ecyo...@grandecom.net]
Sent: Thursday, January 9, 2014
Are you looking to notify the user if your app is running? If not you can use
the CloseApplication util extension that will just shut it down.
JohnG
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn
Any help with some example, thanks
Regards,
Balu
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments
I finally found a solution to this at
http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/ and am
posting my solution should anyone in the future find this post.
In my main file (Product.wxs) the components to install are defined as
follows:
!-- Identify ComponentGroups to be
It's possible that settings of the MSIRESTARTMANAGERCONTROL and
MSIRMSHUTDOWN properties affects this behavior - don't know for sure.
Apart from CloseApplication, the app could integrate with Restart Manager
to shut down - this has the potential advantage that in patching scenarios
the app can
We've decided to go with the approach you've suggested, and I will look into
delta patches to reduce the patch size (although since most of our changed
files will be videos, I would guess deltas wouldn't help much).
As far as each patch superseding the last, is this something we need to
specify
Thank you everyone. After much research and many difficulties, I finally
figured it out with the help of your replies (special thanks to the winded
reply by Blair). According to a comment on Rob's Remember Property blog, I
also found out that WiX 3.5+ supports firstSequence on SetProperty so
Depends what caused the error.
-Original Message-
From: Parm [mailto:sfbu...@gmail.com]
Sent: Thursday, January 9, 2014 11:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] No Error message prompt
More general question is:
If there is any error happened, what's the way
More general question is:
If there is any error happened, what's the way to force Installer to prompt
error message? My installer just stops quiet without any message. The only
way is to look the log file.
Thanks,
Parm
--
View this message in context:
thanks for the reply.
The error I am trying to handling is about certificate. For example:
iis:Certificate Id=SSLCertificate Name=Test.cer
CertificatePath=[SSLCERTIFICATE] Request=no StoreLocation=localMachine
StoreName=root PFXPassword=[SSLPASSWORD] /
if user provide wrong certificatePath or
That's an extension that gets backed by a custom action. It depends what the
custom action does. That happens to be a WixExtension so you have access to all
the source code.
-Original Message-
From: Parm [mailto:sfbu...@gmail.com]
Sent: Thursday, January 9, 2014 11:39 AM
To:
We ship a MSI which supports upgrades. We schedule the RemoveExistingProducts
custom action after InstallInitialize using MajorUpgrade
element –
MajorUpgrade
Schedule=afterInstallInitialize
AllowDowngrades=yes /
The MSI performs a variety of things including GACing,
23 matches
Mail list logo