First a disclaimer, I haven't actually done this!
VS Solutions are nothing but groups of projects, you can have one solution
which has the projects you want to build and another solution that includes the
Votive projects that you use with Visual Studio.
It's not that hard to create an MSBuild f
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.
ing 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 0
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 prop
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 a
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 b
[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 "unava
ter
tengineering.com> Bob Arnson ,
Sent by: [EMAIL PROTECTED]
wix-users-bounces cc
@lists.sourceforg wix-users@lists.sourceforge.net
e.net Subject
Re: [WiX-users] Using WiX v3 Votive
to build WiX v2 projects
06/09/2007 15:55
Please respond to
[EMAIL PROTECTED]
engineering.com
[EMAIL PROTECTED]
wix-users-bounces cc
@lists.sourceforg wix-users@lists.sourceforge.net
e.net Subject
Re: [WiX-users] Using
I'm afraid v2 won't cut it for me then. I'm actually using TFS Team Build and
I need the project document to be MSBuild also so I can just call the solution
build. Using v3 against v2 binaries seems to work though.
Bob Arnson <[EMAIL PROTECTED]> wrote: Christopher Painter wrote:
> I was unde
Christopher Painter wrote:
> I was under the impression from various postings that Votive v2 wasn't
> as stable/complete as the rest of the toolset and that the real work
> was done in v3.
That's correct. You asked about MSBuild. WixTasks.dll and wix.targets
are the MSBuild tasks and targets,
.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christopher Painter
Sent: Thursday, September 06, 2007 1:51 PM
To: Bob Arnson; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using WiX v3 Votive to build WiX v2 projects
I was under the
I was under the impression from various postings that Votive v2 wasn't as
stable/complete as the rest of the toolset and that the real work was done in
v3. I'll go back and give it a try though and see how it works.
Bob Arnson <[EMAIL PROTECTED]> wrote: Christopher Painter wrote:
> Problem is
Christopher Painter wrote:
> Problem is WiXAware authors WiX v2 schema and WiX v2 doesn't have
> MSBuild support.
It does. WixTasks.dll and wix.targets ship with v2.
--
sig://boB
http://joyofsetup.com/
-
This SF.net emai
I also wonder if what I'm doing has some issues, whats the chances that Votive
could be adapted to support building either v2 or v3 schema ala MSBee style.
Christopher Painter <[EMAIL PROTECTED]> wrote:I have some merge modules
that contain thousands of simple `xcopy` files that I'd like
I have some merge modules that contain thousands of simple `xcopy` files that
I'd like developers to maintain. I don't want to use VDPROJ because it's slow
as hell and sucks at MSBuild support and I don't want to use InstallShield
because it costs too much to give everyone a license.
I ca
16 matches
Mail list logo
