To get back to your original question where you're setting $(WixToolPath) to
point to the 2.0 versions. That should work fine unless you try to pass in
arguments that only the 3.0 versions support. I don't remember off the top
of my head what those new properties are, but you'd probably learn pretty
quickly when you get build errors. The WiX project property pages within
Visual Studio are targeted for the 3.0 versions and not all of the various
checkboxes and other settings will work when using the 2.0 candle/light/lit.

 

There are no plans to touch Votive v2 in any way and all active development
is being done against Votive v3. You could log a feature request, if you
wanted, to add the ability in Votive v3 to target a v2 candle/light/lit. To
be honest it probably won't happen (at least for a long time) simply because
I'm working on other higher priority features, but it's a nice idea.

 

And why'd you have to throw in that last jab about "InstallShield has been
doing it for years"? J

 

Justin

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Thursday, September 06, 2007 6:11 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using WiX v3 Votive to build WiX v2 projects

 

The finer points of MSBuild/Team build are getting lost in these replies so
it's kind of pointless to continue.    VDPROJ and WiX v2 are proper
comparisons because both have .xxproj files that are NOT MSBuild files.
Whether or not they `support` MSBuild is a non issue.    For example to
build both you could use an Exec to go out of process and call devenv
solution /build project but thats really ugly as it adds another dependency
to the build box.

 

For Matt, I'd suggest that you just start wiring it up and what I've posted
previously will quickly become obvious.   WiX v3 with it's native MSBuild
project format is just so much  more cleaner and powerful from a TFS
perspective.  It also happens to be the way InstallShield has been doing it
for years...



Bob Arnson <[EMAIL PROTECTED]> wrote:

[EMAIL PROTECTED] wrote:
> I'm interested to know why V2 won't work for you as it does provide
support
> for MSBuild?
>
> My understanding of Votive is that it enables WiX projects to be viewed in
> VS, still in there text\xml format. If the project is there but Votive
> isn't VS marks it as "unavailable". If that's the case MSBuild will still
> build it... or no?
> 

Yes, it will. Votive v2's project files aren't based on MSBuild; Votive 
v3's are. But both WiX v2 and v3 include MSBuild tasks and targets and 
therefore both can be built from TFS Build.

The same isn't true of .vdproj files, which are still not based on MSBuild.

-- 
sig://boB
http://joyofsetup.com/



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

 

  

  _____  

Sick sense of humor? Visit Yahoo! TV's Comedy
<http://us.rd.yahoo.com/evt=47093/*http:/tv.yahoo.com/collections/222>  with
an Edge to see what's on, when. 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to