Hi,
Have you migrated from Wix v1 to Wix v3?
What are the risks?
What are the areas to focus?
Is there any tool to migrate Wix v1 to Wix v3?
Will WixCop help in anyway?
Could you please give me a general idea?
Thanks,
Walaja
--
Quick stroll through the RTM source dump reveals the following:
7 extensions have localized strings:
ComPlus
Firewall
IIS
MSMQ
SQL
UI
Util
5 of those extensions have only en-US strings included:
ComPlus
Firewall
IIS
MSMQ
SQL
Util also has de-DE (but only those two languages), and UI has a total
I'll preface this by saying that I'm not very experienced using Wix so I may be
doing something wrong. I'm attempting to use the FirewallExtension. When I
build in English it succeeds. However, when I build using other languages it
fails. I get the following error:
C:\delivery\Dev\wix30_public\
I've seen some comments suggesting that file costing gets slower when the
current TARGETDIR is populated, and if that's the case it presumably makes the
costing calculations more complex The same might be true if other target
folders are populated (and that's more speculation). Nevertheless, ta
Blair,
I didnt get one. If I see it happen again, I most surely will. As I
said previously, I am not sure what it was I was installing or for that
matter what OS (though the choice is either XP or Vista). Its also
entirely possible the application I was installing was not my own
WiX-generat
I want to update my machine.config to create the element in
system.web if and only if it does not already exist. Then I want to
update the retail attribute to be set to "true" no matter whether or not
the element existed before the install began. Here is my
WiX snippet:
This is off-the-cuff, but is it possibly related to generating the "System
Restore Point"? I have seen that take a "long" time before.
Did either Alex or Chris happen to obtain a log?
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Wednesday, September 16, 2
Chris gave it several minutes, I let it sit overnight. So there is a problem.
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, September 16, 2009 10:46
To: wix-users
Subject: Re: [WiX-users] (no subject)
Pally,
I, like Alex, have seen the same thi
Some practical considerations: Both the Module and the Product elements
contain a required @Language attribute. If the Package element's @Language
attribute is missing, the parent's Language value will be used instead.
Since Heath suggests always making sure both language values are the same,
to pr
Pally,
I, like Alex, have seen the same thing and recently too. As I recall, I
waited several minutes for an installer to "think" before I got bored
and cancelled it. I just put it down to Windows being "awkward" as when
I restarted the installer, the thinking time was either non-existent or
Hi Gábor,
Our product's installer originally suffered from the same problem as Lian -
that the dialog text displayed in English on all systems. While researching the
problem, I stumbled across the blog post that Blair mentions below, and that's
what lead me to experiment with the summary infor
This is the blog entry I was referring to last night:
http://blogs.msdn.com/heaths/archive/2006/10/25/how-windows-installer-uses-l
anguages.aspx.
You will notice he refers to two places where language is identified in the
MSI files, and where each of those two settings takes effect.
-Original
They did push MSI 4.5 in Vista SP2, and Win7 has MSI 5, which includes
everything in 4.5. But there are not any planned future service packs for XP
that I know of...
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, September 16, 2009 2:51 AM
To: Gen
Hi,
i have written the following code in wix to build a localhost db2 odbc
driver connection.
.msi is running without any problem.
First question is about the written code, is it right to build the
connection? or missing something?
Second question how can i check whether the connection was succes
On Wed, 16 Sep 2009 10:07:55 +0100, Michael Bednarek wrote:
Mike,
> value of this attribute is "1033" then the text will always display
> in English, even on non-English systems. If you want the text to
> display in the system language, you can set the value of the
> attribute to "0" (language ne
Windows Installer doesn't support running multiple installations
concurrently as it's a transaction based system. Not sure how burn works
as I've not upgraded to WiX v3.5 yet but dotnetinstaller
(http://dotnetinstaller.codeplex.com/) is a pretty easily configurable
bootstrapper for this type of thi
Actually, I've found that the language of this initial dialog depends on the
languages that your MSI publishes in its summary information stream. In WiX,
this corresponds to the value of the "Languages" attribute of the "Package"
element. For example, if the value of this attribute is "1033" the
Hi Ranganatha,
Thanks for example.
Checking the DB2 installation on target machine is wokring now.
Best Regards
Adnan
Ranganatha H C wrote:
>
> Hi,
>
> One way would be to add Registry serach and assign the registry serach
> result to a property. Later you can use the property based on its v
That means Windows Installer is "thinking". We get it with patches when
you click on the Next button on WelcomeDlg as at that point the Windows
Installer is inventorying the product's currently installed components &
keypaths etc. Not sure what would cause it with an MSI, possibly a large
number of
I had never really thought about bootstrapping WI v4.5 with Installer.
Does WiX 3.0 support
Windows Installer 4.5
Or alternatively how can I check if v4.5 is installed so I can throw up
an conditional message.
Dominique.
-Original Message-
From: Pally Sandher [mailto:pally.sand..
The list server generally strips attachments.
Before Windows Installer has finished parsing the MSI database file to
determine what language it is in, it uses the user/system locale to show the
first messages. One of the core wix-team members blogged about that (it
seems like it was 3-4 years ago?
I'm pretty sure Octopus (being someone who has not actually used it) has an
option to enable MSI logging. You received the generic "installation failed"
error result. You will need to look at the MSI logging to determine the
reason for the error.
The "Failed to create web application" message has
22 matches
Mail list logo
