Hi Bob,
I'm really blank about using this variable "DelayStart" for 5sec ,please
guide me to do this.
thanks for your reply.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Uninstall-and-Repair-not-working-tp7590029p7590069.html
Sent from the
SignCabs only signs cabs that are not embedded in the MSI (external cabs). WiX
does NOT provide any target explicitly for signing your payload before it is
cabbed (or any other such manipulation of your payload).
You can either write a Binder Extension that ensures that files are signed
before
The only idea that occurs to me is to provide the manual as a payload only to
the MBA and to pass its location to the MSI via an MSI property that you use in
the CopyFile table.
Blair
From: Michael Stoll
Sent: Wednesday, October 23, 2013 3:31 AM
To: General discussion for W
Not sure, but did you try setup.exe /install /silent "InstallFolder=C:\Program
Files (x86)\XXX" ?
Blair
From: tom
Sent: Wednesday, October 23, 2013 1:14 AM
To: General discussion for Windows Installer XML toolset.
I am using such command line for my MBA
setup.exe
Hey Phil, not all files are xml some are MVC html views, we would rather
replace all the files than let the user try to merge changes back into their
dev or live environments. I saw someone else asked a similar question
yesterday on overwriting all files on repair which is basically what happen
Search this list. It’s been discussed several times.
Blair
From: Robert Nell
Sent: Tuesday, October 22, 2013 4:47 PM
To: General discussion for Windows Installer XML toolset.
Can a bootstrapper with multiple chained MSIs be made to avoid multiple
Add/Remove Program entri
If it finds the one installer package and not the other, and they are both
using a similar path, that smells like a bug to me.
Blair
From: Pally Sandher
Sent: Tuesday, October 22, 2013 2:58 AM
To: General discussion for Windows Installer XML toolset.
It may well do that
It’s a combination of setting “DisplayInternalUI” to “yes” AND setting the
“display” arguments to BOOTSTRAPPER_DISPLAY_PASSIVE (which happens for you when
you pass the “/passive” argument to burn). That will get you
INSTALLUILEVEL_REDUCED (4). INSTALLUILEVEL_BASIC (3) isn’t currently available
Dear users,
I can't found how to set UILevel == 3 or 4 for msi (MsiPackage).
DisplayInternalUI='no' sets UILevel == 2 (INSTALLUILEVEL_NONE)
DisplayInternalUI='yes' sets UILevel == 5 (INSTALLUILEVEL_FULL)
Yours sincerely.
---
I would choose "none of the above." :) The primary reason to use
filtering is when you're choosing files individually, based on what you
know about changes made to the product. Otherwise, use no filtering to
get the default automatic behavior. I'm not aware of any problems using
Melt and automa
Ok, good to know. I have thousands of components though spread across a dozen
features. Those features are shared amongst 8 products :)
When I originally developed the Products I thought I was being clever by
logically grouping certain ComponentRefs into component groups, and those
groups wou
On 26-Oct-13 05:15, John Ludlow wrote:
> I don't think the standard bootstapper application's theming is capable of
> that kind of customisation.
That's correct. It would have to be a feature of WixStdBA.
--
sig://boB
http://joyofsetup.com/
--
On 28-Oct-13 20:38, Tunney, Stephen wrote:
> Adding DirectoryRef to the same boat as FeatureRef. I've added all
> directoryRefs, including the one that includes the component that I know has
> been updated and still no dice. :(
When used in patch family filtering, only a ComponentRef will includ
On 28-Oct-13 04:43, Selva wrote:
> *1. To show the Splashscreen i have applied *"DelayStart"* for 5sec but its
> not working.
There's no variable used for that purpose.
> 2. During UnInstall, the VBagent.msi is not getting uninstalled when we
> uninstall the Master Package.
Check the Burn log to
Adding DirectoryRef to the same boat as FeatureRef. I've added all
directoryRefs, including the one that includes the component that I know has
been updated and still no dice. :(
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: October-28-13 7:41 PM
To:
Hello again everyone,
Ok, so I've finally managed to get a patch generated. Good for me, I get a
gold star :)
Now I have a few questions
1) It looks as through using FeatureRef in my PatchFamily doesn't work.
The result is an empty CAB file and a pyro.exe error PYRO0227
2) If I s
Hello,
I understand restartresource is only available on vista and up. I'm trying
to restart explorer on install and after uninstall because I have a
contextmenu attached to the shell.
I only see explorer restarting on an upgrade, but not on install or
uninstall. I have taskmanager running and s
Bug 4168 created
Cheers,
Stephen
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: October-28-13 11:56 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Purely WiX Patching when a patch family consists of
component groups across multiple cabs
On 28-Oc
It's safer strategy in these cases to update the existing file, and not
destroy data that the user or the system may have entered. It should be
just an Xml update, right?
Phil Wilson
On Mon, Oct 28, 2013 at 5:47 AM, Christoffel le Roux <
christoffe...@flowcentric.com> wrote:
> Hi, When try to p
I have put nothing in the GAC myself. Just thought that since melt.exe could
not find the binaries it needed that perhaps it was looking in the GAC as part
of its references.
It also need the compression DLL as well. Manually copying the files to the
bin folder fixed the issue.
Could I be mi
On 28-Oct-13 11:21, Tunney, Stephen wrote:
> Now I am getting an error in melt.exe. Looks like a path issue or WiX DLLs
> not being added to the GAC for some reason. Copying files from the SDK
> folder to the bin folder have resolved this issue but this is likely a bug in
> 3.7's installer.
As
I don't think the installer ever puts Wix into the GAC, which is by design. If
you've put some of the Wix binaries in the GAC, I could see that leading to all
kinds of strange issues.
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: Monday, October 28,
Ok, working through my own issues here. Starting to use MELT for fixing my
wixpdb issues as per:
http://www.joyofsetup.com/2013/07/16/easy-pure-wix-patching-with-melt/
Now I am getting an error in melt.exe. Looks like a path issue or WiX DLLs not
being added to the GAC for some reason. Copyi
I've gotten a little further. Now the pyro call is complaining that it cannot
find a bunch of files, but it is looking in the folder location that the
original (1.0) MSI would have gotten its source files from, and not where the
files exist on the machine that I am trying to generate the patch
You can do something called Version lying. Basically you author your WXS
to say the text file has a version number and now it'll always reinstall.
There are some down sides though.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Forcing-overwr
ite-of-text-file-td711667.html
On 10/28/2013 1:35 PM, Andrew Makhorin wrote:
> Is there any way to tell the installer to always install original files
> provided in .msi on repairing/reinstalling the product?
See
http://technet.microsoft.com/en-us/library/cc759262%28v=ws.10%29.aspx?ppud=4#BKMK_Repair
.
--
Bruce
--
On Sun, 2013-10-27 at 05:53 -0700, Christopher Painter wrote:
> This is normal as the Windows Installer will generally attempt to preserve
> user data during installation. See:
>
> http://msdn.microsoft.com/en-us/library/aa368599(v=vs.85).aspx and adjacent
> pages.
>
Thank you very much for y
it is working now, though I'm not really sure what I did to make to work.
I think messing around with the build template's 'Clean Workspace' setting
did the trick. Hopefully, I won't end up in the odd state again.
Now on to my next question...(I'll start another thread).
On Fri, Oct 25, 2013 a
Hello,
I'm trying to check if the same version of my bundle is already installed. I
know that downgrades are already checked by the bundle engine. But, to avoid
duplicate entries of my bundle with same version i'm using this condition:
...
...
This works perfectly for me. But,
Hi, When try to patch non-versioned files, the files does not get replaced when
the file on the disk was changed by the user, I know this is by design, but I
need to patch some configuration files that the user was allowed to update,
lets say it's a web.config file, when some additional content
Should be possible using Win32_ReadFile + Regex_Replace + Win32_WriteFile +
from Msiext (AppSecInc. Community MSI Extensions -
http://dblock.github.io/msiext/)
--
October Webinars: Code for Performance
Free Intel webinars c
I have created a bundle with "Three MSIs" ,
1. microsoft.interopformsredist.msi
2. VBagent.msi
3. .NETApp.msi
During Installation its working fine,below are issues that needs to fixed
during Uninstall and Re-Install
*1. To show the Splashscreen i have applied *"DelayStart"* for 5sec but its
not
Yes, i have used the DisplayName . I do not think that it corresponds to
"Title" in the summary information stream.
To be more clear, this is what i want populated:
-When you right click on a .msp file in windows explorer, there is a section
called "Description" under the Details pane.
-Under thi
33 matches
Mail list logo
