Hi Rob,
Thank you for your reply. The code page you suggested worked a treat, it also
worked for Vietnamese which is a bonus.
Best regards,
Dave
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 23 October 2011 17:56
To: General discussion for Windows
I was hoping output from heat payloadgroups and containers would help me
understand how to create such an animal. Where do you suggest I look for
clues on how to take a legacy install and containerize it?
Rob Mensching-7 wrote:
Heat has lots of gaps. It's an area for us to invest in WiX v4.
Verifying the signature verifies the hash of the file. It allows you to
change the exact file as long as the signature is still valid. The behavior
you see is by design.
Checking the hash on an unsigned file means it has to be exactly the same
file when burned. Not so for a signed file. This
1) It would be nice if it just logged retries by default and immediately failed
only if I configured XmlFile to do so or if the retry loop was exhausted. It
would also be nice if the message was more direct and more like a warning by
default instead of implying that the install had failed.
2)
Hi,
As part of a setup logic, I need to leave behind a big chunk of resources on
disk at uninstall. The resources are data files and I have been asked to leave
them behind at uninstall. When the setup is run again on the machine where this
data is left behind, the user has the option to use
Dear All,
We would like to display before entering the Execute sequence the list of
features that the user selects to install, but do not know what the best
approach would be. Specifically, the implementation involves getting the
feature install status and organizing the features to install
I'm just starting to use Burn and was wondering if it's possible to use
it to simply 'wrap' an MSI as a .exe and have it not show any of its own
UI? That is, launching the executable should only show the internal MSI
interface. Is that possible using the standard BA, or would I have to
write
In what kind of situations would you recommend using the wcautil
custom action scripts (WcaCaCreateScript, etc...) instead of
serializing data into the CustomActionData property?
Thanks,
Bill
--
The demand for IT
On 24-Oct-11 16:02, Bill Tutt wrote:
In what kind of situations would you recommend using the wcautil
custom action scripts (WcaCaCreateScript, etc...) instead of
serializing data into the CustomActionData property?
Only when an immediate custom action cannot determine the machine state.
The
On 21-Oct-11 19:52, john.burak wrote:
Anyone know, is this perhaps a minor bug in the UI/dialogs, Candle, or
Light? It might make my QA person happy to know it's been reported ;)
Nope. ARP/PF doesn't do a wholesale refresh of the program list for MSI
packages. When you click Uninstall and it
On 19-Oct-11 13:36, Gregory Swanson wrote:
But maybe you are right about the components. The files are in the same
directory location, but the IDs and GUIDs of the components have
changed. If that is the issue, it would be difficult to fix because we
create the Wix code using an automated
On 19-Oct-11 08:27, Thomas Due wrote:
However, I still need to know how I pass a command-line argument to the
application I run on ExitDialog exit.
That's not supported by shell execute. Use
CustomAction/@FileKey,@ExeCommand.
--
sig://boB
http://joyofsetup.com/
On 24-Oct-11 10:10, David L. Beckwith wrote:
I was hoping output from heat payloadgroups and containers would help me
understand how to create such an animal. Where do you suggest I look for
clues on how to take a legacy install and containerize it?
Maybe you could explain what containerize
You'd need to write your own. The wixstdba is not about showing the MSI UI.
I bet if you wrote one some other people would like to use it. it is
definitely possible since we added MsiPackage/@DisplayInternalUI (or some
attribute named similar to that).
On Mon, Oct 24, 2011 at 11:28 AM, Bruce
1. Don't try to leave a Feature behind. It'll drive you crazy.
2. I'd probably try this... or use no GUID if you don't want to manage the
data at all.
3. Custom actions are an admission of failure:
And the Windows Installer will not treat you well if you violate the
component rules:
http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101 .
On Mon, Oct 24, 2011 at 8:25 PM, Bob Arnson b...@joyofsetup.com wrote:
On 19-Oct-11 13:36, Gregory Swanson wrote:
But maybe you are right
FYI: I was a very unhappy setup developer when I had to create those
functions. They go against all good practices. Avoid at all costs.
On Mon, Oct 24, 2011 at 8:33 PM, Bob Arnson b...@joyofsetup.com wrote:
On 24-Oct-11 16:02, Bill Tutt wrote:
In what kind of situations would you recommend
17 matches
Mail list logo
