Did you borrow VC's MSM's package guid for your MSM?
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Sunday, January 29, 2012 11:35 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
On 27-Jan-12
As has been mentioned on this list before, properties go just one way
between UI and Execute sequences. It is by apparent design that you can't
change a property (any property) in the execute sequence and pick up that
change in the UI sequence.
-Original Message-
From: John Cooper
If you mean if I've used guids which are also used in the VC MSM, then
no. I've tested this by generating completely new guids for my merge
module, and still I got the warnings.
Thanks for the idea though, didn't think of this obvious error...
-Original Message-
From: Blair
Do the dll version numbers change automatically in the build ?
-Original Message-
From: john.burak [mailto:john.bu...@telvent.com]
Sent: 26 January 2012 18:21
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Our WiX patch installer is very slow
As a follow up to my last
Sorry, I'm not sure why you're getting a long delay there.
The difference in patch size might be due to InstallShield using delta
patching and Wix using whole file patching. Look in the property pages for
the InstallShield patch.
If that isn't it, try comparing the patches with Orca/InstEd and
Rob,
I just assumed that it was a bug because your response to that Stack
Overflow question stated that the behaviour being seen was a bug. I didn't
know enough about working with Burn to know if I was doing something wrong
or if it was a problem with Burn but I accepted that you would know what
I know that this email thread is very old, and I know that the tool in WiX
only covers immediate actions (not deferred actions) but I don't think
deferred custom actions can be fully unit tested on a build machine anyway,
but can the Lux tool meet the need for unit testing your CAs?
Blair
The only reason I asked is because the guid that suffixes the property names
is supposed to be the MSM's Package @Id, and there should be no reason that
your MSM is using another MSMs properties. However, that appears to be a red
herring (the duplicate sequence number warnings are expected in that
Hi,
I am using Windows 7, 64 bit.
I ma having trouble reading if a key exists in registry. The key that I am
using for is in HKLM\Software\Wow6432Node\MyApplication\MyApp.
I am using the following code:
Property Id=ISPRESENT
RegistrySearch Id=PathSearch
Root=HKLM
Type=raw
For a x64 MSI this should work, for a Win32 MSI you should use
Software\MyApplication\MyApp and let the MSI engine handle the WOW6432 stuff
:)
Best regards,
Albert van Peppen
Senior System Engineer
Insad Grafisch b.v.
-Oorspronkelijk bericht-
Van: loyalty Reddy
You're trying to search WoW6432Node from a 32-bit process. It doesn't exist in
that context. Remove it from your Key it'll magically* work.
*Note: no actual magic is involved as it's a fictional concept which doesn't
exist. The Windows-on-Windows subsystem does all the clever stuff redirecting
And how can I check if ISPRESENT is empty or not?
On Mon, Jan 30, 2012 at 2:16 PM, Albert van Peppen alb...@insad.nl wrote:
For a x64 MSI this should work, for a Win32 MSI you should use
Software\MyApplication\MyApp and let the MSI engine handle the WOW6432
stuff :)
Best regards,
Albert
I did remove Wow6432Node and also Win64 element. I just want to know at the
end if ISPRESENT is empty ot not. HOw do I check that? If ISPRESENT is
empty, I want to enable a control.
On Mon, Jan 30, 2012 at 2:29 PM, Pally Sandher pally.sand...@iesve.comwrote:
You're trying to search WoW6432Node
Hi,
I added an icon to my bundle, the bundle executable now shows an icon in
explorer. However, when started I still have no icon showing on the
top-left corner of the stdba. I am using a 32x32 ico file specified in
Bundle/@IconSourceFile. Am I missing something?
Cheers:Peter
You can use ISPRESENT in a condition wherever you like; for example in enabling
a button in your UI.
Read the tutorial on how to use condition on the appropriate place :)
Best regards,
Albert van Peppen
Senior System Engineer
Insad Grafisch b.v.
-Oorspronkelijk bericht-
Van: loyalty
Control ...
Condition Action=enableNOT ISPRESENT/Condition
/Control
Palbinder Sandher
Software Platform Engineer
T:
+44 (0) 141 945 8500
F:
+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
thank you all very much. I am able to get it working
On Mon, Jan 30, 2012 at 3:17 PM, Pally Sandher pally.sand...@iesve.comwrote:
Control ...
Condition Action=enableNOT ISPRESENT/Condition
/Control
Palbinder Sandher
Software Platform Engineer
T:
+44 (0) 141 945 8500
F:
+44 (0) 141
My logo is 64 x 64 pixels, RGB color without transparency, safed as png
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundled-MSI-branding-tp7228010p7236961.html
Sent from the wix-users mailing list archive at Nabble.com.
I just upgraded from v3.6.2520.0 to v3.6.2527.0 and noticed that the cached
files from the old version are still in the cache (along with the new
files).
I am wondering if this is the expected behavior or not.
Here are the contents of the log file:
---
And here is the log from the uninstall of v3.6.2520.0
--
[0DD4:0DD8][2012-01-30T10:56:55]: Burn v3.6.2520.0, path:
C:\ProgramData\Package
Cache\{c18586f8-ce3c-4cb7-b003-162f6b341878}\WiX36.exe, cmdline: '-uninstall
-quiet -burn.related.upgrade
Maybe in WiX v4. Not doing those sorts of large changes to non-Burn related
features in WiX v3.6 or v3.7.
On Tue, Nov 29, 2011 at 8:27 AM, Christopher Painter chr...@iswix.comwrote:
I don't think Jason is involved in WiX / DTF development anymore. Can
anyone confirm or deny?
I'd do the
Maybe I should be more clear. When I say something is a bug, I mean The
behavior you described is not expected. That does not mean there is a bug
on SourceForge tracking it.
Privileged in Burn means the process was launched elevated. If you are
launching Burn elevated (aka: you see the consent
I think there is a bug that the wixstdba is not always getting it's icon
set correctly in its window. If that isn't open, please feel free to open
it.
On Mon, Jan 30, 2012 at 6:59 AM, Peter Bulyaki peter.buly...@gmail.comwrote:
Hi,
I added an icon to my bundle, the bundle executable now shows
No, that'd be a bug. It'd be great if you coudl attach your log files to a
bug.
On Mon, Jan 30, 2012 at 8:18 AM, jhennessey jack.hennes...@hyland.comwrote:
And here is the log from the uninstall of v3.6.2520.0
--
AH! My image was much larger. It was truncating at 64x64 I think. I just
shrunk down to 64x64 and it shows up correctly.
Thanks much!
On Mon, Jan 30, 2012 at 10:47 AM, ACKH forforumh...@hotmail.com wrote:
My logo is 64 x 64 pixels, RGB color without transparency, safed as png
--
View
Well, can't say I didn't offer. Even if it did take 2 months for someone
to notice.
And when is 4.0 scheduled for? 2015? (frustration)
From: Rob Mensching r...@robmensching.com
Sent: Monday, January 30, 2012 11:11 AM
To: chr...@iswix.com, General
I created SF Bug 3481704 for the issue (log files attached to bug).
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-6-Upgrade-Leaves-Files-in-Cache-v3-6-2520-0-to-v3-6-2527-0-tp7237051p7237232.html
Sent from the wix-users mailing list archive
And in the verbose log, see if there are any SELMGR entries. They indicate that
you've broken component rules during a patch by deleting a component. Otherwise
look at the log to see what it says about that particular file and why it
didn't replace it.
Phil W
-Original Message-
Hi,
I noticed that Burn moves the payload to Cached Directory during uninstall
even though the ExePackage/@Permanent=yes is set, tried to search the bug
list see if there's any related issue about it but no luck. Is this by
design?
The problem is if the Payload is too big like 1000s of files, it
Does burn support variables in a bundle like the setup does? I have
added my custom bootstrapper and MSI as references and used the
variables, it compiles; however when running the installer it just
shows the splash screen before dying. Below are the bundle and burn
log.
?xml version=1.0
Thank you, Bob and Blair.
I moved the Custom element to InstallUISequence like:
InstallUISequence
Custom Action=SetExitDialogOptText Before=ExecuteAction
NOT Installed
/Custom
/InstallUISequence
and the problem was resolved!
On Mon, Jan 30, 2012 at 12:09 AM, Blair os...@live.com
Does anyone know if there is a limit to the number of packages that can be
applied at once with MsiApplyMultiplePatches() or
Installer.ApplyMultiplePatches() in DTF? I've run into an issue where 84
packages will apply fine, but 85 and above results in a 1601 error code.
I've tried varying the
What is the Detect and Plan state for the ExePackage?
On Mon, Jan 30, 2012 at 10:16 AM, Romeo S. dfox.mxyzp...@gmail.com wrote:
Hi,
I noticed that Burn moves the payload to Cached Directory during uninstall
even though the ExePackage/@Permanent=yes is set, tried to search the bug
list see
I hope WiX v4 starts in 3 or so months. When is it done... depends how much
we decide to put into it.
On Mon, Jan 30, 2012 at 9:16 AM, Christopher Painter chr...@iswix.comwrote:
Well, can't say I didn't offer. Even if it did take 2 months for someone
to notice.
And when is 4.0 scheduled
If you mean preprocessor variables? Yes, those are the same (they are
handled by the preprocess which runs before the compiler). You might try
running dark -x dumpfolder path\to\bundle.exe and see what is in the
manifest. It is possible your preprocessor variable is not resolving to
what you
How does burn determine the class to run? The name of the dll? If so
can it be set in configuration?
Dieter Lunn
http://ubiety.ca
On Mon, Jan 30, 2012 at 10:45 PM, Rob Mensching r...@robmensching.com wrote:
If you mean preprocessor variables? Yes, those are the same (they are
handled by the
Assembly attribute.
// Identifies the class that derives from BootstrapperApplication and is
the BA class that gets
// instantiated by the interop layer
[assembly: BootstrapperApplication(typeof(WixBA))]
On Mon, Jan 30, 2012 at 9:00 PM, Dieter Lunn coder2...@gmail.com wrote:
How does burn
Thanks. I completely forgot that part.
Dieter Lunn
http://ubiety.ca
On Mon, Jan 30, 2012 at 11:10 PM, Rob Mensching r...@robmensching.com wrote:
Assembly attribute.
// Identifies the class that derives from BootstrapperApplication and is
the BA class that gets
// instantiated by the
38 matches
Mail list logo
