It really depends on what those 9k scripts are doing.
If your scripts are a raft of INSERT statements or other transactions, then you
can probably switch to CSVs and bulk load (much faster), which is what we do
with AdventureWorks now for SQL Server 2008 samples. The WiX3 code for ours is
check
My application installs on a per-machine basis so that it is available to
all users. I have InstallPrivileges=elevated and InstallScope=perMachine. In
addition, the installer creates some registry entries for my application in
HKLM because I have specified Root=HKMU.
I would like to set some d
How do you know the DLL is not extracted, versus some other problem executing
it? It's not clear from the log below. Keep in mind that when extracted it
actually has the filename extension .TMP instead of .DLL.
On the failing system are there any unusual filesystem permissions in the
\Windows\I
I can't seem to get rid of this error on my server builds:
1/23/2009 2:57:48 PMCMD:
E:\bt\512100\build\setup\tools\wix\3.0.4707.0\binaries\light.exe -ct 16 -v
-pedantic -ext WixUIExtension -ext WixNetFxExtension -cultures:en-us -loc
E:\bt\512100\build\setup\tools\wix\3.0.4707.0\sources\loc
What version of the WiX toolset are you using?
-Original Message-
From: Adam Eversole [mailto:adam.evers...@microsoft.com]
Sent: Friday, January 23, 2009 14:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Adding system wide module to IIS7 on 64-bit OS
I have a setup that inst
I have a setup that installs a system-wide managed-code module in IIS7. I do
this as follows:
With the following preprocessor command setting var.64bit:
This seems to work just fine in 32-bit, but in 64-bit it fails with the
following
I am creating a SQL database with my installer. Right now I have
approximately 9000 scripts to be run after the database is created. This
is taking around 20mins for the install to complete. Is there anything I
can do to speed this process up? I thought about running a single
script to restore the
Poo.
Well, thanks anyway! -- Daí
-Original Message-
From: Brian Simoneau [mailto:bsimon...@freedomscientific.com]
Sent: Friday, January 23, 2009 10:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Modify behavior of tree selection control?
This is
Windows Installer doesn't support that so the WiX toolset can't either.
-Original Message-
From: Corry, Davidson [mailto:davidson.co...@sage.com]
Sent: Friday, January 23, 2009 10:47
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Modify behavior of tree sel
This is not possible with a Windows Installer tree control. You will need to
write your own.
-Brian Simoneau
-Original Message-
From: Corry, Davidson [mailto:davidson.co...@sage.com]
Sent: Friday, January 23, 2009 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subje
I think there are some WiX built-in custom actions that set permissions - I
forget if it's Permissions or something else.
Phil Wilson
-Original Message-
From: Thomas Due [mailto:thomas@scanvaegt.dk]
Sent: Friday, January 23, 2009 1:17 AM
To: General discussion for Windows Installe
(Sorry if this is an FAQ. If so, I haven't found it yet, and please
point me to it.)
I want to modify the context-menu that appears when you click
on the drive+arrow icon in the standard feature-selection control,
on a per-feature basis. Specifically, I need to
* no "entire feature will be insta
Wouldn't surprise me if #2 is the issue. You'd have to follow up with the
Windows Installer team to know for sure...
-Original Message-
From: Adam Burton [mailto:adz...@googlemail.com]
Sent: Friday, January 23, 2009 10:36
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Preve
Well, further developments :-).
I never got round to specifically creating a verbose log under the conditions I
suspected were causing the reboot. Instead it happened again today, but this
time I noticed that the MsiInstaller outputted a list of files that were locked
and what processes were lo
Nope, sorry. I don't use DTF.
-Original Message-
From: Alex DeNeui [mailto:al...@docverse.com]
Sent: Friday, January 23, 2009 10:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one
machine)
Hi Rob -
Hi Rob -
I upgraded to 3.0.4805.0 but that does not solve the problem.
Any ideas on how to debug what could be going on?
alex
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Friday, January 23, 2009 1:23 AM
To: General discussion for Windows Installer X
Neither really. The application itself contains no user specific files
so to me, it doesn't matter. Are there any specific reasons why you'd
want one over the over?
My major concern was to remove the Installshield version which I now
know is per-machine.
Chris
-Original Message-
Fro
I tried to reproduce the problem again last night by getting a changeset which
showed the problem but, of course, everything is working now. *sigh*
We use subversion here. I have two Intel Xeon 3GHz procs with 2GB RAM. I'm
running Windows Server 2008 but a colleague first saw the problem on his
In article ,
Chris Lord writes:
> I have two further questions
> 1) Would it be possible to set ALLUSERS and then detect the previous
> products and if found, give a warning and exit the installer. If a
> previous product isn't found then clear all users and continue with the
> inst
Thanks Richard, I kind of guessed that was the case.
I have two further questions
1) Would it be possible to set ALLUSERS and then detect the previous
products and if found, give a warning and exit the installer. If a
previous product isn't found then clear all users and continue with the
I am in the process of creating a Visual Studio package. Wix works
really well for making installer for it.
However, I am unable to figure out how to install help collection from
a *.HxS file.
Could you please point me to a complete example of a WiX source file
which makes an installer for a help c
You can't upgrade away a per-machine install with a per-user install
and vice-versa. The best way to handle this is to set ALLUSERS
according to what was installed previously and not let them change it
during the upgrade. Another way of dealing with it is to cope with it
in a bootstrapper and fo
You can't update a per-machine install from a per-user install (or vice versa).
It's an inherent limitation.
There were some threads on this earlier and you should be able to find them via
search.
From: Chris Lord [chris.l...@atterotech.com]
Sent: Friday
Hello,
I have a Wix installation built to replace an Installshield one.
However, on testing, some files are updated but add remove programs
contains uninstalls for both the original software and the Wix installed
one. I used the same Upgrade code as in the previous Installshield
versions.
I
No idea, but 3.0.4318.0 is a really old build.
-Original Message-
From: Alex DeNeui [mailto:al...@docverse.com]
Sent: Friday, January 23, 2009 01:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Managed CA fails to extract to temp directory (on one
machine)
Hi all -
I have a
Hi all -
I have a managed CA created using DTF and WiX (3.0.4318) that is failing with
MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it.
The exact same MSI works fine on multiple XP and Vista machines. I spent some
time looking into the issue, and it appears that on
It was the account name. I changed it to "NT AUTHORITY\NetworkService"
and presto: It installed without a hitch.
Now I only have a single question (at the moment): How do I set specific
permissions to a specific account on the installdir?
I need to set write permissions for "NT AUTHORITY\NetworkSe
Hello Bob,
I am not sure how I can specify this property in the project file - there is
no such option over UI.
Could you please provide me with an example for the project file with
setting the property?
Thanks,
Dmitry
Bob Arnson-6 wrote:
>
> Dmitry Ponomarenko wrote:
>> I am in trouble with
28 matches
Mail list logo
