Bob Arnson wrote:
> Search the log for SELMGR.
The log files do not contain it...
From: Adrian Gantoi
To: General discussion for Windows Installer XML toolset.
Sent: Mon, November 9, 2009 5:14:48 PM
Subject: Re: [WiX-users] Product uninstall problem when re
The safest way requires that you prepare both admin images and call torch
twice, once for the English old against the English new and the other time
for the Spanish old and Spanish new. You then need to supply both wixmst
files to pyro by supplying the -t argument twice. This means you will be
usin
Looking at the 3.0 RTM help chm, here is what I see:
Try removing RelativePath attribute entirely from the Class element.
-Original Message-
From: Roy Chastain [mailto:r...@roychastain.org]
Sent: Monday, November 09, 2009 12:52 PM
To: General discussion for Windows Installer XML toolset.
I don't know, but it may have been one of those bugs that was punted for 3.0
and fixed in 3.5.
You could search the bugs to see if there was a workaround listed for 3.0
(which is one reason it may have been punted, assuming it was filed against
3.0), or you could use 3.5. The core toolset for 3.5
Hello,
I've seen multiple similar posts but none seemed quite what I was looking
for, sorry if this has already been answered.
We have released one MSI for each language we support - each with it's own
ProductCode and CodePage.
Using Wix only patching, I thought it should be possible to sp
Note: I forgot to mention that I removed the ScheduleReboot and I did not get
the error message.
John L Krupka wrote:
>
> The setup executable that I am building with setupbld using the setup.exe
> stub crashes with a "The process terminated unexpectedly" message box.
> The install requires a
The setup executable that I am building with setupbld using the setup.exe
stub crashes with a "The process terminated unexpectedly" message box. The
install requires a reboot, so the ScheduleReboot action is called. The
crash occurs after the reboot dialog is cleared. It does not matter how the
I have the following XML
Candle indicates the error is on the statement. I have tried
this with as a descendent of File and as a descendent of AppId
(as shown). Same error message in both cases.
What does this error message really mean?
-
Version 3.0 (final version) will not allow DllSurrogate="" on the AppId.
It says that if I want an empty string to remove the attribute.
Current build of 3.5 will allow DllSurrogate="".
If the attribute is removed, there is no entry in the Registry table for
the DllSurrogate value and that is not
Maybe this is not a great place to ask, but if you know -
I wonder if there is a way to install the .NET 3.5 framework by showing
non-English language on GUI. Is it possible?
I tried "dotnetfx35setup.exe /lang:FRA", but it still shows English.
Thanks.
From: l
Thanks Blair.
After removed those curly braces, it works.
I'll log a bug.
Thanks again.
From: Blair
To: General discussion for Windows Installer XML toolset.
Sent: Friday, November 6, 2009 6:56:44 PM
Subject: Re: [WiX-users] Some text on progress dialog
Ok, that's much better.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, November 09, 2009 10:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing PDBs
John H. Bergman (XPedient Technologies) wrote:
> I was just
Dan Giambalvo wrote:
> So, is there any way to work around this issue? Is there something I can do
> in the handler of my button to cause a focus change before I invoke my CA?
>
I'm not aware of any.
--
sig://boB
http://joyofsetup.com/
--
John H. Bergman (XPedient Technologies) wrote:
> I was just curious if there was an easier way of installing PDBs? What I
> have works, but it seems cumbersome.
>
How so? They're just files. Try dropping the Id and Name attributes; WiX
provides defaults for them.
--
sig://boB
http://joyofs
Алексей Далекин wrote:
> I'm using WIX v3 to install my filter driver. The driver is installed
> correctly but DeleteFiles option doesn't work.
>
You'd have to take that up with the DifxApp folks; WiX just wraps their
custom actions.
> I need to remove *.inf, *.sys files from my InstallFolder
Adrian Gantoi wrote:
> The installation was successful, even with MSIENFORCEUPGRADECOMPONENTRULES=1.
>
Search the log for SELMGR.
--
sig://boB
http://joyofsetup.com/
--
Let Crystal Reports handle the reporting - Fr
or more simply the setup.exe version just goes straight to "Resuming install.."
instead of "Welcome to install" ?
From: warne...@hotmail.com
To: wix-users@lists.sourceforge.net
Subject: setupbld setup.exe & repair install
Date: Mon, 9 Nov 2009 15:57:31 +
Hi there,
I am using setupbld t
Hi there,
I am using setupbld to create a setup.exe from my msi. Using the command:
SETUPBLD -title "MyApp" -ms MyAppSetup.msi -setup setup.exe -out MyAppSetup.exe
However, I get a strange difference between the exe & msi installer version.
Running the installer with the application already in
Hi there,
I am using setupbld to create a setup.exe from my msi. Using the command:
SETUPBLD -title "MyApp" -ms MyAppSetup.msi -setup setup.exe -out MyAppSetup.exe
However, I get a strange difference between the exe & msi installer version.
Running the installer with the application already in
Hi all,
OK, re-run the installation for the faulty case (build 1.1 + SP2 patch) with
logging all the way...
The installation was successful, even with MSIENFORCEUPGRADECOMPONENTRULES=1.
I looked at the log files with the help of Windows Installer Verbose Log
Analyzer tool,
and none of the 4 logs
I was just curious if there was an easier way of installing PDBs? What I have
works, but it seems cumbersome.
It seems to me that must be an easier way, but I have not been able to locate
anything related to installing PDBs. PDB deployment makes live de
Could you check the msi.dll file in both computers and see if they are the
same version?
-Original Message-
From: PitMonster [mailto:peter.bra...@grutzeck.de]
Sent: Sunday, November 08, 2009 11:07 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Text randomly disappearing
Perchance did you remove any components in your SP2 patch?
Set MSIENFORCEUPGRADECOMPONENTRULES=1 in both commandlines when rerunning
the scenario. If you get an installation failure that should point you to at
least one component rule violation that will produce the effect you are
describing.
---
If you do any of these three things:
1) use either the C/C++ runtime MSMs
2) install drivers using Difxapp
3) install stuff using either GAC or WinSxS (that is: if any of your File
elements contain an Assembly attribute set to anything except "no")
then there are upgrade scenarios (even with major
Create a LaunchCondition by placing the following element under your Program
element (anytime after the Package element):
NOT VersionNT64
-Original Message-
From: Lukhnos D. Liu [mailto:lukhnos...@lithoglyph.com]
Sent: Monday, November 09, 2009 1:01 AM
To: wix-users@lists.sourceforge.net
Hi Rob,
thank you for the hint, it has solved my problem.
My condition for the UI now uses the action state of the feature and
replaces '&' with '&'. Then it works fine:
&Feature2=3
Thomas
Rob Mensching-7 wrote:
>
> I think you need a & or ! before the Feature Id. Take a look at the
> "Cond
Hi all,
I have the following problem with our installer for which we deliver a service
pack (patch) setup.
We use for the setup and patch build the WiX build 3.0.4014.0.
Situation is as follows:
a) we built (and shipped) our product MSI (let's call it build 1.0).
b) we built (and shipped) a full
2 ways to achieve it off the top of my head.
1 - Easy way, use the Major Upgrade functionality. See the How To at
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm (also in the
WiX.chm). This requires the original MSI created in WISE to have an
UpgradeCode set in it. Having never used WISE
Dieter if you read Luknos' e-mail you should see the reason why he would
like to disallow installing the x86 package on x64 platforms (see 3rd
sentence).
Rob Hampflett already posted one solution but a simpler way to achieve
this would be to add a Condition element inside your Product Element to
c
Hi there
Since ClickThrough is not ready yet, can anyone suggest what other
alternatives are available?
I googled some third party software that seem to handle auto upgrade but
I'm not sure how well they work.
http://www.catenalogic.com/products/updater/information
http://www.autoupdateplus.com/
Adding tags like these should do it:
Please use the 64-bit installer
VersionNT64
Rob
Lukhnos D. Liu wrote:
> Hi,
>
> When the Platforms property of the Package tag is set to x64, the built
> package becomes 64-bit-only and will not install on 32-bit Windows.
>
> Is there a way
Why would you want to? a 64bit computer can run 32bit applications it
just can't be done the other way around hence the restriction. If you
must you might might have to do the detection and blocking yourself.
Dieter Lunn
http://www.coder2000.ca
On Mon, Nov 9, 2009 at 3:01 AM, Lukhnos D. Liu
wr
Hi,
When the Platforms property of the Package tag is set to x64, the built package
becomes 64-bit-only and will not install on 32-bit Windows.
Is there a way to do the reverse, i.e. disallowing a 32-bit-only package to be
installed on 64-bit Windows? This is because we have two versions for th
33 matches
Mail list logo
