Hmm,
3000 files shouldn't be that bad... Are these data files which aren't
versioned? I wonder if it's doing some hash calculations to see if it needs to
repair the files (and as such is reading all the files from disk and computing
the hash). Also, do you have anti-virus software running on
Hi,
Thanks Blair.
So, the discovery time can not be more quickly??? I think one minute is too
long for waiting for installing. It is just "prepare" and the install is not
start even.
If i do not use the build-in UI, i think, the discovery time is as long as
using the build- in UI.
Thanks for info on HKMU. I'll give it a try and suppress ICE57 on the compile.
Is HKMU a WiX thing or did I miss a Windows installer acronym meeting?
Dave Williamson
-Original Message-
From: "Hoover, Jacob"
Sent: 12/4/2013 8:11 PM
To: "General discussion about the WiX toolset."
S
HKMU is either HKLM or HKCU depending on if it's a per user or per machine
install.
Note, I have disabled ICE57, as I am using HKMU registry resources for the
shortcuts. Windows Installer complains
about per-user data and a keypath that can be per-user or per-machine.
There are numerou
Yes there have been. That is why we held at 2.0 and didn't make the jump. We
recently ran across the issue where a msi built in 2.0 installs under program
files(x86) on x64 machines no matter what. So rather than beat that horse we
are putting the time into migrating.
Dave Williamson
Clear Sky
As I recall, there were major language changes from 2.0 to 3.0 and that
refactoring would be expected. 3.0 - 3.8 should generally be backwards
compatible though.
From: "Dave Williamson, Clear Sky Software"
Sent: Wednesday, December 04, 2013 4:50 PM
To:
Context is a migration of a WiX 2.0.5805.0 solution to WiX 3.8.1128.0.
Seemed to be working through the compiler and linker errors one by one just
fine until I hit ICE38 regarding shortcuts. There are 2 shortcuts created
to the same installed EXE. One shortcut is in the start menu and the other
i
There's nothing wrong with a sequence of InstallExecute, REP,
InstallFinalize at the end of the execute sequence - it's one of the
choices documented in MSDN. Some rambling thoughts/brain dump to think
about:
1. Are you sure you haven't overlapped the Progid element with the registry
stuff? I'm pre
Hi,
I'm writing a bundles to chain some installs together. Currently this is
WiX 3.6, though I'll be considering an upgrade to 3.8 at some point. The
bundle uses the RtfTheme theme, customized with the
bal:WixStandardBootstrapperApplication/@ThemeFile attribute.
My question is this: Is there a wa
Done. It's bug
Bug 4221
William D. Hayden
Eastern Skies District
Camping Chair
Technology Chair
From: Blair Murri-3 [via Windows Installer XML (WiX) toolset]
To: wdh61
Sent: Wednesday, December 4, 2013 4:50 AM
Subject
You can’t skip CostFinalize, but if you don’t use the “built-in” Windows
Installer UI, you can skip the “UI sequence” (by doing your UI outside of MSI,
say in a bootstrapper).
Windows Installer is a declarative, transactional system, and it compares your
desired state against the system’s curr
I didn’t miss it. I mentioned it in the paragraph starting “The biggest missing
piece”.
Discussing the other question should be in a different thread, but the short
answer is: that isn’t quite the model used with burn. Query the archives of
this list for details (I suggest using the query stri
It was my mistake , I have tried building wix instead of the DevBundle.
I download, compile and install the DevBundle, but the errors with building wix
are present, that I mentioned below.
The following actions (here is the source
http://sourceforge.net/mailarchive/message.php?msg_id=31536281
Hi all，
I have a problem with wix.
There are about 3000 files in my msi and it is about 500M. When I run it at
first time, it is quickly. But if the program was already installed in the
computer, when I run another msi (the same msi, but build again) it will spend
too much time on the prepare d
Just curious: MSDN says that LoadBitmap() is deprecated, and to use LoadImage()
instead. I wonder if that makes a difference with the BMP version used.
Would you mind opening a bug? I would like to test this scenario out.
-Blair
From: wdh61
Sent: Tuesday, December 03, 2013 12
Search the archives of this mail list
-Blair
From: dileep s
Sent: Wednesday, December 04, 2013 1:24 AM
To: General discussion for Windows Installer XML toolset.
Hi All,
How do I prevent the Bootstrapper.exe after triggering MSI?
Is there any solution to hide the Bootst
Hi All,
How do I prevent the Bootstrapper.exe after triggering MSI?
Is there any solution to hide the Bootstrapper main UI until MSI is
progressing?
Thanks in advance...
--
Sponsored by Intel(R) XDK
Develop, test and di
The DevBundle branch doesn’t have any of the tools that crashed for you.
There’s no build directory created in the DevBundle branch either. It has an
SLN file you can load into Visual Studio (if you have WiX installed already) or
build using MSBuild (also requires WiX available) that contains ju
Windows Installer is designed to work with UAC by delaying the UAC prompt as
long as possible. There is no way to alter that without bootstrapping the MSI.
Normally that shouldn’t matter because immediate custom actions should never be
changing anything on the computer. It’s only an issue in th
19 matches
Mail list logo
