WiX v3.6 Beta does not support VS 11. You need a more recent build from
http://wixtoolset.org/releases
On Fri, Mar 2, 2012 at 7:53 AM, Raphael Schweizer <
rschwei...@schweizer-informatik.ch> wrote:
> Hi WiX users
>
> Rob Mensching wrote:
> > Latest WiX v3.6 builds support Dev11. You may need to r
IIRC, that's how that API works.
On Fri, Mar 2, 2012 at 7:02 AM, Andy Clugston wrote:
> I am working with the Windows Installer APIs (msi.dll). I would like to be
> able to harvest the paths of file components of certain products installed
> on the system. I am currently using the automation int
The custom action scans a root directory and adds the necessary
RemoveFile/RemoveFolder temporary rows to the MSI (as it is runnin) and the
Windows Installer handles deleting folders and rolling back and all that.
On Fri, Mar 2, 2012 at 2:36 PM, victorwhiskey wrote:
> I've been trying to understa
On 02/03/2012 21:55, Larry Fluckiger wrote:
> I'd love to see the new look. Can anyone point me to some screenshots?
There's a screenshot at
http://www.joyofsetup.com/2012/01/22/the-new-wixtoolset-org-and-weekly-builds/
--
Bruce Cran
I'll post one when I install it on my notebook this weekend.
-Original Message-
From: Larry Fluckiger [mailto:larry...@microsoft.com]
Sent: Friday, March 02, 2012 3:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wow!
I'd love to see the new look.
I've been trying to understand this, but how would it help if you don't know
what's goign to be written upfront?
Rob Mensching-7 wrote
>
> Use the RemoveFile or RemoveFolder element. If you don't know everything
> up
> front, add temporary rows to those tables. The wix-contrib project on
> codep
I'd love to see the new look. Can anyone point me to some screenshots?
- Larry
-Original Message-
From: John H Bergman (XPedient) [mailto:john.berg...@xpdnt.com]
Sent: Thursday, March 01, 2012 8:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wow!
It
I can detect REPAIR by setting a custom property. Here is how I did it: In my
MYWIXUI_MONDO.wxs file, I specified values for CUSTOMMODE property as below. I
than detect the value of CUSTOMMODE in CustomAction and perform actions
accordingly.
1
1
1
1
1
1
An option I use on the candle command line is just to pass an arg of
*.wxs rather than calling each. Likewise on the light command I pass in
*.wixobj.
I find it cuts down on the length of the command line.
-Original Message-
From: Ian Williams [mailto:iawil...@microsoft.com]
Sent: Thursd
Why do you want to do that? The usual way to assemble wixobj's is to use a
Library project to assembly them into a wixlib. If you turn binding on, this
also includes the binaries referenced by the wixobj's making the wixlib
freestanding. Wix and VS will handle the linking for you if you set a
Hi WiX users
Rob Mensching wrote:
> Latest WiX v3.6 builds support Dev11. You may need to run devenv.exe /setup
> right now... we're trying to track down a real answer on that.
Any hints how to get that to work? I downloaded and installed WiX 3.6.2221.0
but had no WiX project types in VS 11.0.50
Can someone please send me an example of the light.exe command to combine two
.wixobj files residing in the same directory?
Thanks
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use o
I am working with the Windows Installer APIs (msi.dll). I would like to be
able to harvest the paths of file components of certain products installed
on the system. I am currently using the automation interface and what I am
finding when calling get_ComponentPath() is that the full path is only
ret
When I use RegistrySearch elements, I generally have them as children of
Property elements. If that is the case for you, a PropertyRef to the wrapping
Property element would do the trick.
--
John M. Cooper
-Original Message-
From: jhennessey [mailto:jack.hennes...@hyland.com]
Sent: Fri
Yes, if you reference anything in a fragment it brings in the entire fragment
(not just the element you referenced).
It doesn't look like there is a RegistrySearchRef element (perhaps submit a
feature request). So, I would recommend putting the searches in an include
file so you can pull them in f
Hi all,
Hope you can help me with this one. I have been google-ing but found no
solution.
What I have done is upgraded from Wix v3 to Wix v3.6 (because of VS2010
support). I have managed to get everything working just fine except for
when building a patch. I get this warning from pyro.exe
pyro.
16 matches
Mail list logo