You can get a log of the install and each entry will contain a time stamp. To
get a full log run
msiexec msifile /l*vx log.txt. I usually find that just using msiexec
msifile /leavx
log.txt gets me most of the information I need.
Rob
On 07/10/2010 21:21, Lena Vinogradov wrote:
Hi ,
I
Is it best practise for the installer to create all the registry keys
that the application itself might create? I imagine the biggest pros to
that would be that the installer controls the default settings, also
making them configurable on the installer command line, and also the
keys will
On Friday 08 October 2010 10:36:12 Mark Simonetti wrote:
Is it best practise for the installer to create all the registry keys
that the application itself might create? I imagine the biggest pros to
that would be that the installer controls the default settings, also
making them
Hi all,
I once again require you expertise;
I have a registry key that I need stored [ok so far], the value is set
to a property which changes on a radio button selection.
However the key value only ever takes the default value of the property,
it doesn't pick up the change when a
Additionally, you may get upgrades, patches and automatic repairs
recreating the keys and values, depending on what you do with them and
if they are keypaths.
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: 08 October 2010 12:26
To: wix-users@lists.sourceforge.net
Hi All,
I created a Custom Action dll (.NET) for a test solution. In this solution
I have the CA project, a simple test app project and a WiX setup project.
This works fine. I'm now trying to take the CA dll produced by this test
solution into our live project. I've copied both dlls (the
That problem can be mitigated:
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original
Thank you, I see in the log that it is in fact spending 9 seconds out of 20 of
total for creating restore point.
Is there a way to specify this MSIFASTINSTALL property value from within Wix?
I mean something like:
Property Id=MSIFASTINSTALL Value=1 /
Would it overwrite the built-in MSI
Yes, you can safely specify Property Id=MSIFASTINSTALL Value=7 / code
(as sample) for enabling this option. This property will be ignored for
Windows Installer prior to 5.0 and will be used under installer 5.0. This
code will not override MSIFASTINSTALL property, this code will set value for
this
Hi, since you didn't include how your includeing the CA it it's hard to help.
This is how I include mine.
Binary Id=InstallHelper
SourceFile=..\InstallHelper\bin\$(var.Configuration)\InstallHelper.CA.dll/
CustomAction Id=GetSqlServers BinaryKey=InstallHelper
DllEntry=FillServerInstances
I have recently migrated from Wise to WiX. I have approximately 150 merge
modules (at some point in the future I may be able to implement libs instead
of merge modules, but for now .) and several installs that include some
subset of the merge modules. I have implemented a VS solution for all the
Thanks very much to all who answered.
My installer takes only 10 seconds total now on Win7.
-Original Message-
From: Alexander Kozlenko [mailto:alexander.kozle...@hotmail.com]
Sent: Friday, October 08, 2010 11:33 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re:
I haven't spent a huge amount of time on this topic because we are generally
happy with our build time, but I can imagine merge modules are disk i/o
intensive not cpu / memory intensive. There is a lot of copying going on to
get the files, create the cabinet and stream it into storage.
13 matches
Mail list logo
