That would be cool but I'm going to hold off until I'm fighting with the next
one. This one is doing what I want. I'd say each time I make an MSI you guys
teach me something else.
On Jan 29, 2014, at 12:23 AM, Blair Murri os...@live.com wrote:
Post a URL and we will interpret/educate on the
Are you doing a major upgrade or a recache/repair?
Are the files it was killing off in the same feature as other files that were
changed? Remember that features are installed/repaired/removed as a unit.
Your verbose install logs should be telling you why it wanted to “replace”
files that
And there's the answer. They're all in the same feature.
Can I move existing files between features in an upgrade? That would position
me better the next time around.
On Jan 28, 2014, at 4:36 AM, Blair Murri os...@live.com wrote:
Are you doing a major upgrade or a recache/repair?
Are
You could move files (strictly components) around, but in most
installs the features are units of functionality and not random
collections of assorted files. A feature is the user's unit of
functionality that can be added or removed, and moving files out of
one often requires other changes such
In my case the installer is always run as quiet and there's no interactions
with any user. Our goal is to slip in and deliver stuff without their
noticing.
I naively put everything in a single feature. it sounds like I would be
better served to sort the files into features based on actual
So far as the logs, I have yet to ever find anything I can make sense of in
an MSI log. I'm well aware that's my own deficiency but those things are
99.95% unintelligible to me.
On Tue, Jan 28, 2014 at 2:46 PM, Walter Dexter wfdex...@gmail.com wrote:
In my case the installer is always run as
Msi logs definitely have a LOT of information in them and can be really
hard to comprehend, but I've found that being able to understand them is
the most important ability for analyzing msi problems (at least for me).
One thing that helped me a lot to understand how to interpret them is this
Post a URL and we will interpret/educate on the interpretation thereof
Walter Dexter wfdex...@gmail.com wrote:
So far as the logs, I have yet to ever find anything I can make sense of in
an MSI log. I'm well aware that's my own deficiency but those things are
99.95% unintelligible to me.
On
]
Sent: Saturday, January 25, 2014 9:12 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Install busy executables at reboot - Windows 7
I tried MSIRMSHUTDOWN = 2, and REBOOT is = ReallySuppress. Behavior is
the same - with /quiet it just quietly kills the exe off
2014-01-27 Walter Dexter wfdex...@gmail.com:
Got it!
I haven't worked out all the details but changing the MSIRMSHUTDOWN
property to 0 makes it do what I wanted. Note that in this case the .exe
files that I want to keep running aren't actually being modified. Our
deployment folks just don't
I believe that is only true for versioned files, although I may be mistaken.
In this particular case (properly versioned .Net 3.5 executables) they were
unchanged and should not have been replaced according to my, and your,
understanding of the rules. Despite that, Windows Installer was killing
busy executables at reboot - Windows 7
I have an embedded system running Windows POSReady 7 (Windows 7 for
POS
devices.)
I have an MSI that installs a collection of .Net .exe files,
VBScripts, and other stuff.
Three of the executables are always running under a user account
[mailto:wfdex...@gmail.com]
Sent: Friday, January 24, 2014 8:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install busy executables at reboot - Windows 7
I have an embedded system running Windows POSReady 7 (Windows 7 for POS
devices.)
I have an MSI
]
Sent: Saturday, January 25, 2014 9:12 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Install busy executables at reboot - Windows 7
I tried MSIRMSHUTDOWN = 2, and REBOOT is = ReallySuppress. Behavior is the same
- with /quiet it just quietly kills the exe off, without
I have an embedded system running Windows POSReady 7 (Windows 7 for POS
devices.)
I have an MSI that installs a collection of .Net .exe files, VBScripts, and
other stuff.
Three of the executables are always running under a user account. That's
just a normal thing on this device - it boots,
What about the MSIRMSHUTDOWN property and maybe the REBOOT property.
-Original Message-
From: Walter Dexter [mailto:wfdex...@gmail.com]
Sent: Friday, January 24, 2014 8:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Install busy executables at reboot
16 matches
Mail list logo
