Thanks Rob for your reply. I did it using custom actions.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Friday, September 12, 2008 2:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Reading the
Hi,
I successfully converted an InstallShield project to WIX 3.
when i tried to add a new custom action - it failed on
MsiGetProperty(hInstall, szName, TEXT(""), &nSizeCount); (gets nSizeCount ==
0 & return ERROR_MORE_DATA), while i was trying to get the CustomActionData
property from the msi packa
In my setup.wixproj I added the proposed Message command to the following
Target setting and it did successfully dump the list of full culture specific
TargetPath build output list as the last output in the build output window.
So the trick I guess to processing the list of culture specific ou
q1 - In the new wix3 way patch msp generation xml is there a way to specify the
element to cover get the msp patch generated to cover changes to
all components from v1.0 to v1.1 versus having what appears to be the need to
specify every component explicitly as the patch help document sample syn
Thanks. I'm now using the following Patch.wixproj postbuild events to
automate the generation of msp output using either new wix3 way or old msimsp
way.
Patch.wixproj | postBuild event
move /y "$(Ta
Thanks that appears to be exactly what my issue was with my adminInstall
output. I used orca to reconfigure the feature level settings in my v1.0 msi
so I could generate a useable adminInstall of it and configured my in progress
v1.1 sources to instead use the following feature install conditio
Hi,
I have a similar problem but with slight change. What i am trying to
achieve is:
I have one .cmd file which i want to run (using custom action) only if user
pass some flag from command line. Just like you did in the example below,but
i want to control my custom action from this flag.
e.
Robert O'Brien wrote:
> it possible to include the ServiceControl statement in my "Service1"
> component and condition it to do an stop prior to files being processed
> during (UPGRADINGPRODUCTCODE Or PATCH) activities and then started after the
> (UPGRADINGPRODUCTCODE Or PATCH) activities compl
Robert O'Brien wrote:
> The syntax of the command is incorrect.
>
That message is coming from cmd.exe; you need to put it in a target instead.
--
sig://boB
http://joyofsetup.com/
-
This SF.Net email is
On Sat, 13 Sep 2008 21:41:09 -0700, [EMAIL PROTECTED] wrote:
Greenaj,
> get these? I am just about ready to create my own proof of concept
> package for calling DTF managed CA.
If you create one that you're ready to share, I'd be very much willing to put
it into the tutorial. I don't have much
It's working as I wanted it.
Thx You both guys!
Bob Arnson-6 wrote:
>
> polan wrote:
>> Just one last question to make it clear : To make it work I need to move
>> the
>> creation of All the xml config nodes to WIX (.wxl) file, and simply
>> forget
>> about copying the app.config file from the
Since the last release of our (Java-based) software we are using WiX 3 to
build the Windows-installer, but the installer is far from being perfect. We
don't have the time to do it ourself and hence need one who can do that for
us (of course paid). Here are details which need some (re)work:
- Ea
12 matches
Mail list logo