The "automatic match" based on the transform having the same name as the
locale id is officially unsupported by Windows Installer. Usually when
something is officially unsupported, something goes wrong when you try it at
some point in the system.
My recommendation is to always use the bootstrapper
2010/1/18 Bob Arnson :
> On 1/15/2010 2:52 AM, Robert Barnes wrote:
>> actually a part of my product! However this same dll is used by both
>> my product and the other program - same dll, same name but installed
>> into two different directories, so the other program is not actually
>> using the dl
Our installer supports multiple languages. We are using the trick from
here(http://jpassing.com/2007/06/14/authoring-multi-language-msi-packages/).
Basically these are what we do:
- We compile the wxs files
- then link with different languages(we support en-US, es-ES, fr-FR, de-DE,
pt-BR and it-
Here are my code. I also added custom actions that are related to
upgrade section.
Thank you very much.
NEWFOUND
NEWFOUND
On Tue, Jan 19, 2010 at 3:59 PM, Blair wrote:
> Please post everything you have in your *.wxs and
Yes, that should work.
-Original Message-
From: Lian Jiang [mailto:jiangok2...@gmail.com]
Sent: Tuesday, January 19, 2010 10:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] how to create a DisplayResourceDll for ShortCut
element
Thanks for reply B
Please post everything you have in your *.wxs and *.wxi files that falls
inside of any tags.
-Original Message-
From: CP YEH [mailto:ntde...@gmail.com]
Sent: Tuesday, January 19, 2010 9:18 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How can I ski
In article
<89030b4a18eccd45978a3a6b639d1f24030ac82...@fl01exmb01.trad.tradestation.com>,
Tony Juricic writes:
> At which point in the patching process are custom actions that are
> executing the updated ones?
If they are custom actions that execute out of installed files, the
updated act
At which point in the patching process are custom actions that are executing
the updated ones?
I have custom actions that execute before and after PatchFiles action.
Custom action executing before PatchFiles finds MSI DB already transformed.
Based on that I would expect that table containing cu
Yeah Neil,
thanks for correcting me ... sometimes brain do go wrong doing multitasking
:)
On Tue, Jan 19, 2010 at 8:59 PM, Neil Sleightholm wrote:
> >> used cmdbld.exe shipped with WiX 3.0...
>
> I think you mean setupbld.exe
>
> Neil
>
>
> ---
Thanks for reply Blair.
My shortcut points to a managed exe instead of a native exe. Can I use a
native resource dll for DisplayResourceDll in this way:
Thanks.
Regards
Leon
On Mon, Jan 18, 2010 at 5:55 PM, Blair wrote:
> Sample code. Take it for what it is worth. This assum
Thank you very much for your reply. I am sorry to bother you but it is
not quite obvious to me how to alter installer's behaviors. My code
does check for upgrade and set certain property if it is upgrade but I
just do not know how to pass this value to actions/UIs.
For instance, I have a code that
There is[are] a property you associate with the previous product(s) that you
will remove/replace when performing your upgrade. The UpgradeVersion
elements that don't have OnlyDetect set to yes. If any of them are populated
then you know that you are upgrading. You can use that in your conditions to
Also, everyone that follows you would appreciate if you contribute the fixes
back to the community.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, January 19, 2010 2:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-u
Hi,
I have posted a question yesterday about minor upgrade and it seems to
me that it would be better to use major upgrade.
However, with major upgrade I want to know how I can skip some actions/UIs.
Here are my requirements.
- I do not want to remove some configuration files that the user has
s
>> used cmdbld.exe shipped with WiX 3.0...
I think you mean setupbld.exe
Neil
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities fo
used cmdbld.exe shipped with WiX 3.0...
now eagerly waiting for the Burn utility (
http://robmensching.com/blog/posts/2009/7/14/Lets-talk-about-Burn ) that
will be shipped along with WiX 3.5 where we can set some look and feel as
well.
On Mon, Jan 18, 2010 at 7:39 PM, akash bhatia <911ak...@gmail
Post the relevant sections of code e.g. the dialog where you ask the
user for the installation directory, any associated properties and/or
custom actions & the section of the directory tree it relates to so we
can try & see what's going wrong. Also looking at a verbose log (msiexec
/a /l*vx ) migh
Hi,
2010/1/19 Reinier Lamers :
> Besides, if the waiting were the problem, I would expect the installer
> to exit when I quit the application it started. That does not happen
> however. And in the howto in the manual, the customaction is given as:
> DllEntry="WixShellExec" Impersonate="yes" />
A
Hi,
2010/1/18 Blair :
> You need to use the Return attribute, and the value you need is asyncNoWait.
> So, your CustomAction tag should look like this:
>
> DllEntry="WixShellExec" Return="asyncNoWait" />
It appears that one cannot specify 'Return="asyncNoWait"' on a
DllEntry
19 matches
Mail list logo
