Fair enough though I already have some script CAs (just because I hate C++) so they're just as likely to trip an AV scanner.
Thanks
John
On 6/9/06, Derek Cicerone <[EMAIL PROTECTED]> wrote:
Let's just make it known to the proper people that the IIS issue should be at the top of their list
Bob Arnson wrote:
> Peter G. Sakhno wrote:
>> 1) I have set of files each in a separate component. And some of those
>> files are not uninstalled. In MSIEXEC log I found following records for
>> those components:
>> “MSI (s) (C8:9C) [...]: Component: ViewerExeComponent; Installed: Local;
>> Requ
Let's just make it known to the proper people that the IIS
issue should be at the top of their list for fixing :) It's probably a lot
less effort to get IIS working properly again versus having you create a script
CA that will ultimately be bad for your customers (esp since script CAs
routi
Dropping wix-devs. Please don't send mail to both lists unless
the subject applies to both lists.
Chandra Rentachintala wrote:
I want to run the vendor
product msi or setup.exe when that
package is not present
MSI doesn't support multiple simultaneous installation transactio
Ed Russell wrote:
>
>
You need a custom action to access formatted-type strings. Use and schedule it when the other
properties have their values set.
--
sig://boB
http://bobs.org
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https:
Peter G. Sakhno wrote:
> 1) I have set of files each in a separate component. And some of those
> files are not uninstalled. In MSIEXEC log I found following records for
> those components:
> “MSI (s) (C8:9C) [...]: Component: ViewerExeComponent; Installed: Local;
> Request: Absent; Action: Null
Oh, fiddlesticks...
Ok, I guess we'll stick where we are then. I could try and find a version with the XML fix but not the IIS bug but I'm more likely to just write a _vbscript_ CA to write out the value and tell people "it sucks but that's life".
Thanks
John
On 6/9/06, Derek Cicerone <[E
Yes.
From: John Ludlow
[mailto:[EMAIL PROTECTED] Sent: Thursday, June 08, 2006 5:40
PMTo: [EMAIL PROTECTED];
wix-users@lists.sourceforge.netSubject: Re: [WiX-users] XML files and
large chunks of XML
Hmmm...
So at the moment there's no real reason for us to move to 3.0. Does
that mean
Hmmm...
So at the moment there's no real reason for us to move to 3.0. Does that mean that 3.0 has the IIS bug as well?
Thanks
On 6/8/06, Derek Cicerone <[EMAIL PROTECTED]> wrote:
WiX 3.0 will have the same IIS problems as 2.0 - the code is identical for all the extensions shared between
Hi,
You could try using [WindowsVolume] to set ROOTDRIVE
Michael
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Etienne
Grignon
Sent: Thursday, 8 June 2006 7:49 PM
To: WiX users
Subject: [WiX-users] determine the ROOTDRIVE property
Hello,
For the mo
In my installer there are 4 features to customize for a given
machine and
only one of it depends on a vendor package.
I want to run the vendor product msi or setup.exe when that
package is not present
on the machine and corresponding feature is selected, during
my setup sequence.
I have a question regarding the patching strategy for my product.
Currently, each build creates a msi with a unique name such as:
product_2_0_111.msi. This name represents the productname, major version,
minor version, and build number.
As the msi name and version strings change per build,
Yes, i know thanks.
We are planning to have major upgrades too.
--
View this message in context:
http://www.nabble.com/Upgrade-problem-t1755143.html#a4780617
Sent from the wix-users forum at Nabble.com.
___
WiX-users mailing list
WiX-users@lists.so
WiX 3.0 will have the same IIS problems as 2.0 - the code
is identical for all the extensions shared between 2 and 3. I'm not sure
what version of wix (if any) contains the XML fix but not the IIS problem (maybe
something about 1 month old). Perhaps someone else can give some advice on
tha
Ah, ok
I do use the IIS functionality though - do you know if there's a version of 2.0 which has the XML fix but not the IIS bug? It probably wouldn't be massively hard to take out the references to Tallow.
Thanks
John
On 6/8/06, Derek Cicerone <[EMAIL PROTECTED]> wrote:
You should just s
You should just stick with 2.0 (but update to the latest
release). As mentioned below, 3.0 has no advantages for what you need (and
several disadvantages if you use tallow in an unsupported way to generate your
build authoring automatically). Heat does not yet cover all the scenarios
which
Hi Guys,
I'm having some trouble Again! Cheers for the "change" issue btw -
I've got it using repair to update the registry and it all works
great... Anyway - back to the current issue... I have a CustomAction
DLL to update some properties in an installed Access DB. Works fine bu
Ok,
I'll take a look at 3.0. However, some of our stuff (including the project I'm working on) relies heavily on Tallow, so I don't want to break it by dropping in 3.0. In theory, I could just drop in Heat and it'd all work, but I don't see it being that simple - we have scripts that fiddle the
Hello everybody!
I started to use WiX recently and got some difficulties with it.
1) I have set of files each in a separate component. And some of those
files are not uninstalled. In MSIEXEC log I found following records for
those components:
“MSI (s) (C8:9C) [...]: Component: ViewerExeComponent
Tamas Tiboldi wrote:
> i got the package installed. Then i've created the package again. (So i got
> a package with another package ID, but the same product ID, Upgrade ID and
> product version - if i'm correct, this means a small upgrade)
>
The Upgrade element is for handling major upgrades. I
Kalappa Pattar wrote:
Message
Now
whenever I try to install from .msi file it should open”
InstallCancelDialog”.
But
everytime it’s calling “Welcome_Dialog”. Is there anything
that I need to set to display “InstallCancelDialog” whenever the
msi is clicked.
That build is a few months stale and likely has the
issue. You should just try swapping in the latest 2.0 build since it
should have the fix (beware of IIS though - there is currently a nasty bug in
there if you use it). Even if you tweak the length of the column in Orca,
I don't think the
I'm using v2.0.3719.0. If this is fixed in 3.0, then I may trial it now rather than waiting for release. This would save me a whole bunch of trouble if I can get it to work. What were the field lengths adjusted to? In the version I have, it seems to be set to 255 (which I get by opening the .MS
If the limitation is the length of the string in the
column, we should fix that. However, I think these limits were adjusted
upwards a while ago. What version of wix are you using (as reported by
candle /?)?
Thanks,
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of J
WoW.
You are right. i've tested it. it works. thanks a lot.
Tamás
--
View this message in context:
http://www.nabble.com/Upgrade-problem-t1755143.html#a4773512
Sent from the wix-users forum at Nabble.com.
___
WiX-users mailing list
WiX-users@lists.so
Thanks John,
I modified Sequence numbers. It worked
fine.
Since it was the first action to be fired
either using exe or by double clicking msi, So I thought of keeoing same Sequence
number for the both. I was wrong there J
Once again thank you.
Best Regards,
Kalappa Pattar
"I
Have you tried not setting the ROOTDRIVE property at all and letting the
Installer mechanism do it?
You're possibly overwriting the value Windows Installer is giving it.
Rob
Etienne Grignon wrote:
> Hello,
>
> For the moment, the ROOTDRIVE property is set like this in the wix file :
>
>
>
You can't perform the small or minor upgrade without passing in command line
parameters for reinstall. Try
msiexec /i setup.msi REINSTALL=ALL REINSTALLMODE=vomus
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi
Sent: Thursda
Hi All!
I have a problem on the upgrade install...
I've created a setup.msi. The package ID is full with '?'s, so every time
when i create a package, a new GUID will be insterted.
i got the package installed. Then i've created the package again. (So i got
a package with another package ID, but t
Hi all,
I have a requirement to take an old XML file and copy all the settings from /configuration/appsettings (which could be 20 or 30 settings) to the new xml file. I've managed to get this ito a property, but when I try to reference it in the XmlFile element it dies horribly. Now, I'm also s
Hmmm.. Not sure then
I noticed that your conditions aren't mutually exclusive, and the sequence numbers for the two actions are the same. Maybe try making the WelcomeDialog sequence be 1235, so they are different, and modify the condition for that to have "And ISEXE" on the end.
Other that,
Does it work if you change the condition on the InstallCancelDialog to
(Not ISEXE Or ISEXE=0) AND Not Installed
John
On 6/8/06, Kalappa Pattar <[EMAIL PROTECTED]> wrote:
Hi All,
I have a c# application which calls my .msi application.
I will pass a parameter ISEXE=1 while call
There is no tallow for wix 3.0 - its been replaced by
heat. Heat should allow you to create authoring for lots of simple
projects pretty effortlessly (I hope).
I totally agree with your sentiments on 3.0
stability. There's been a few really nasty regressions in the weekly
builds recently
There are two separate issues here:
1. The warning about collisions is just that - a warning. If it doesn't
worry you, then you can simply suppress it with -sw1055 on the light
commandline. The warning is intended to alert you that two different merge
modules are colliding (which should never ha
We had to make some features 3.0-only otherwise no one
would ever adopt it :)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon
TylerSent: Wednesday, June 07, 2006 1:52 PMTo:
wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Unique Short
Names?
I had a funny bu
Title: Message
Hi All,
I
have a c# application which calls my .msi
application.
I will pass a parameter ISEXE=1 while
calling .msi file..
I want to install only through C#
application not by double clicking the ..MSI.
Good to know. However, I think we're waiting till it's at release stage and considered stable. I don't know when that's likely to happen, so for the time being we're with WiX 2.0. I'm hearing good things about 3.0 though - like the fact that tallow will generate fragments that can be plugged str
I got another report of this issue again recently so I
finally looked at in the debugger and it was quite complicated. The UI
extension itself is fine, the 3.0 wix toolset contains a bug in how embedded
binaries are handled from extensions. I've got a fix for the issue and it
should hopefu
Better yet - just use wix 3.0 because it handles the short
file names for you automatically :)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
LudlowSent: Tuesday, June 06, 2006 2:52 AMTo:
wix-users@lists.sourceforge.netSubject: [WiX-users] Fwd: Unique Short
Names?
I
40 matches
Mail list logo
