Hi, we are a requirement to kill Chrome and Firefox during install, so that
we can install or modify a plugin. What is the best way to kill processes
(or ask the user to kill processes)?
Thanks,
Tim
--
Live Security Virtua
I have a property bound to control, named WEBSITEDIRNAME, and I would like to
use the value when creating a instead of
static Name value.
Regards,
Benjamin Fallar III | Microsoft Developer Lead
Avanade Software & Cloud Services (ASCS)
Accenture | Manila
"Plan Ahead. Be Ahead. Plan BCM."
www
Perhaps just a misunderstanding. Could it be that CustomActions have to be
always between and fragments are not exactly extra bits
of the Product?
On Tue, Apr 24, 2012 at 3:37 PM, Rob Mensching wrote:
> Because something is wrong?
>
> On Tue, Apr 24, 2012 at 2:40 PM, E. Timothy Uy wrote:
>
> >
Thanks Rob! I added
http://schemas.microsoft.com/wix/2006/localization";>
[2] has been installed. Click Yes to restart now.
Click No to manually restart later
Which ultimately worked, though it did send my output to bin\Release\en-us.
Is the localization file the only way to do this? I wasn't a
Really? That doesn't work? I kinda' expect it would work. if it doesn't,
the error message from the log file owuld be interesting.
On Mon, Apr 23, 2012 at 5:18 AM, Neil Sleightholm wrote:
> You can't do that but you can create 2 elements one for port
> 80 and other 81 - that has worked for me
That error message must be coming from your custom.dll. I'm a little
confused why the code would be looking for wixstdba data if it's not
wixstdba.
On Tue, Apr 24, 2012 at 10:00 AM, jean claude klodjan
wrote:
> but in that case, the bal:WixStandardBootstrapperApplication element will
> use the o
Please file a bug.
On Tue, Apr 24, 2012 at 10:10 AM, E. Timothy Uy wrote:
> http://wix.sourceforge.net/manual-wix3/specifying_cultures_to_build.htm
>
> The "specifying cultures" link is dead from
> http://wix.sourceforge.net/manual-wix3/build_a_localized_version.htm
>
> -
The log file should show you the command being passed to the executable.
Maybe try that exact command outside of Burn?
On Tue, Apr 24, 2012 at 8:57 AM, Miss Parker wrote:
> Alright, I tried that (/msiexec /qn /i exePath/) and it worked. That can't
> be
> good...
>
> Can you (or anyone else) see a
Add an Error element.
On Tue, Apr 24, 2012 at 9:54 AM, E. Timothy Uy wrote:
> Is it possible to change the reboot message shown for "ScheduleReboot"? I
> would like it to be simpler, something like "[2] has been installed. Click
> Yes to restart now. Click No to manually restart later." I read o
Because something is wrong?
On Tue, Apr 24, 2012 at 2:40 PM, E. Timothy Uy wrote:
> Here's something strange:
>
>Property="QtExecInstallCmdLineRun"
> Value='"[INSTALLFOLDER]xxx.exe" install'/>
> BinaryKey="WixCA" DllEntry="CAQuietExec" Execute="deferred" Return="check"
> />
>
>
Here's something strange:
Not
Installed
Not Installed
Installed
Installed
Placed inside the Product tag, this works, but in a fragment
, it does not. Why?
Thanks,
Tim
--
Bump.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 16 April 2012 17:13
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn: ExePackage display name
Where does the description displayed above the status bar come from for an
ExeP
http://wix.sourceforge.net/manual-wix3/specifying_cultures_to_build.htm
The "specifying cultures" link is dead from
http://wix.sourceforge.net/manual-wix3/build_a_localized_version.htm
--
Live Security Virtual Conference
E
but in that case, the bal:WixStandardBootstrapperApplication element will
use the original wixstd ba -
how can i tell it to use my custom dll ?
2012/4/24 Bruce Cran
> You need to use the bal:WixStandardBootstrapperApplication element to tell
> the ba where to find the license and logo. See the
Is it possible to change the reboot message shown for "ScheduleReboot"? I
would like it to be simpler, something like "[2] has been installed. Click
Yes to restart now. Click No to manually restart later." I read of some
folks using "Error Id=1703" but I'm not sure where to put this.
Respectfully,
You need to use the bal:WixStandardBootstrapperApplication element to tell the
ba where to find the license and logo. See the "changing the wix standard
bootstrapper application branding" topic in the help file.
--
Bruce Cran
Sent from my iPad
On 24 Apr 2012, at 17:31, jean claude klodjan wr
Here's one technique that I find useful
Open the MSI in Orca like normal and then create a transform.
Paste your RTF in like normal and then tell it to Generate the transform.
Close orca.
Now you can use WiUseXfm.vbs to apply the transform to similarly created
MSI's.
http://msdn.micro
I had that issue and found the easiest way to solve it was it was to create a
wixlib using wixstdba.wxs as an example. IIRC you need the code from
wixstdba.wxs in your code somewhere and a wixlib was the simplest way to
achieve it.
Neil
-Original Message-
From: jean claude klodjan [mai
Thanks Rob!
The LicenseAgreement I am trying to import into the Control table is 19 pages
long and it is in rtf format.
So I am not sure how I can import this using that vbs script.
Should I:
* Import using Orca for the first time.
* Get the "formatted text" in the Text column of the Control tabl
hello
i have built a custom bootstrapper application, based on wixstdba.
when i run the bootstrapper built using this dll, it can't probe for the
thm.wxl and thm.xml files.
i have added those files as payload, that way :
this solves that part of the problem, but now i get th
Alright, I tried that (/msiexec /qn /i exePath/) and it worked. That can't be
good...
Can you (or anyone else) see any obvious errors with my ExePackage
definition?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Help-with-silent-install-E
Just try running Update_1.12.10.exe from a command prompt, it none of the
options works silently it doesn't support it. You could also try /? and see if
it supports help.
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 24 April 2012 16:01
To: General di
The exe is a patch and is supposed to support silent install, but maybe it
doesn't.
Do you happen to know any "official" exe's that supports silent install,
that I can download and test with? This has bugging me for days, and it
would be nice to find out if I'm doing something wrong or if the file
Rollback should end up removing all the installed packages. With major
upgrade this *does* leave the old version on the machine in a broken state.
Fortunately, a repair will fix the old version.
MSI does provide a way to put multiple MSIs in a transaction but every time
we try to use it we find a
I would like to launch my application immediately after the installer
reboots. Is setting a runonce registry the best way to do this? If I have a
scheduled reboot, can I make my UI continue and prompt the user to "launch
the application" now?
Not
Installed
Not Installed
You could use the wisql.vbs that comes with the MSI SDK.
On Mon, Apr 23, 2012 at 8:15 PM, Uma Harano wrote:
> Hi Rob
>
> I need to fix the license agreement in a msi file that has already been
> built. I cannot unfortunately rebuild the msi again. So I have been
> "fixing" the msi with the new l
Bug.
On Tue, Apr 24, 2012 at 5:20 AM, Neil Sleightholm wrote:
> I have noticed that in burn the ProgramFilesFolder variable includes a
> backslash at the end and ProgramFiles64Folder doesn't:
> [04F4:06E0][2012-04-24T13:14:52]: Variable: ProgramFiles64Folder =
> C:\Program Files
> [04F4:06E0][201
It will only install silently if Update_1.12.10.exe supports that.
Neil
-Original Message-
From: Miss Parker [mailto:caisa.westl...@gmail.com]
Sent: 24 April 2012 15:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix Burn: Help with silent install (ExePackage>
Hello,
I'm t
Hello,
I'm trying to get Burn to silently install an exe, but I can't get it to
work. Can anyone see what I'm doing wrong?
I've also tried /s, /qn and /silent, but no luck.
The installation starts, but so does the the GUI unfortunately.
Any help is appreciated.
//Caisa
--
View this messag
Thanks for the quick reply but this is for a Burn package rather than a
standard MSI.
Neil
-Original Message-
From: Osanger, Martin [mailto:martin.osan...@fabasoft.com]
Sent: 24 April 2012 14:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - Co
Hello,
If i don't missunderstood you, you can set a property with the correct path
before installation was triggered.
e.g:
.
VersionNT64
NOT VersionNT64
kind regards,
Martin
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Dienstag, 24. A
Hi,
I am trying to populate a registry value in textbox but not being able to
do so. Following is my code:
---
---
--
Thanks and Regards,
Ravi Raj
--
Hi,
This is specially dangerous when we are upgrading an existing installation.
If I have several MSI chained and one of them fails, burn rolls back that
one, but leaves the previous MSIs already updated.
Therefore, I might potentially end up with a broken application after
executing the setup.
Thanks!! :-)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Modifying-MSIs-from-the-bootstrapper-tp7470406p7495882.html
Sent from the wix-users mailing list archive at Nabble.com.
I have created a combined x86 and x64 package by setting the InstallCondition
of my MsiPackages to "NOT VersionNT64" or "VersionNT64" respectively. This
works ok but I can't see how to set the InstallFolder variable so that it is
correct for the options dialog in the StdBA (I can set it correctl
I have noticed that in burn the ProgramFilesFolder variable includes a
backslash at the end and ProgramFiles64Folder doesn't:
[04F4:06E0][2012-04-24T13:14:52]: Variable: ProgramFiles64Folder = C:\Program
Files
[04F4:06E0][2012-04-24T13:14:52]: Variable: ProgramFilesFolder = C:\Program
Files (x86
My policy is always to use a per machine install in roaming profile
environments..
Besides the 'standard' discussion to determine if roaming profiles are a good
idea in an organization.
In most cases you will end up with a fragmented active directory; some users
are with a roaming profile, other
Hi, guys,
We set the target culture of a managed resource dll to zh-CHT , which are
neutral culture identifiers and it can cover all the special cultures under
Chinese traditional categories for example: zh-TW, zh-HK and zh-MO. However
the wix linker( light.exe) generates an error, if we turn
38 matches
Mail list logo
