Which version of TFS are you using?
For 2008, I do the same thing, I actually changed the web service config file
to set the directories, I was able to get it pretty close to our developer
configuration so that I could get WiX working with the same settings for both
environments.
-Original
The easiest way I have found to do this is to maintain multiple
configurations. Use one configuration for the build server and one for
development systems. Then pass in the variable into the preprocessor
variables in the Wix Project.
-Michael Clark
-Original Message-
From: pmdarrow [mailt
The project variable approach (i.e. $(var.ProjectName.TargetDir) only seems
to work if the projects are in the same solution. I have two solutions, the
installer project in one and the DB project in the other. I've come up with
a workaround by making a special case for the build server, but I was
If you install the WiX toolset on the build machine, I believe you can use
the built in project variables to reference the other projects.
On Fri, May 7, 2010 at 6:27 AM, pmdarrow wrote:
>
> Here's what I'm trying to do: I have two solutions - one for my main
> application and its associated pro
Thanks a lot. I will try it out.
Neil Enns wrote:
>
> Here's the documentation I mentioned that should show up in the next
> weekly WiX build:
>
> Integrating WiX Projects Into Daily Builds
>
> One of the most common reasons for using MSBuild with WiX project files is
> to integrate the build
Here's the documentation I mentioned that should show up in the next weekly WiX
build:
Integrating WiX Projects Into Daily Builds
One of the most common reasons for using MSBuild with WiX project files is to
integrate the build of an installer into an existing daily build process. This
is ofte
Sajid,
Create a .wixproj file either manually or using the Votive integration with
Visual Studio, then check that project into TFS. After that's done you can go
through some easy steps to check the WiX tools into TFS and make a minor
modification to the .wixproj file so it will build on your da
Yeah, you can do it. You'll have to manually create your tasks and schedule
them in each of your project files. That's essentially duplicating what's
int he project files for Votive. I would say, even though it's going to be
some work, you'd still be better served by building Votive projects and
Hi,
If I use votive, its going to be a lot of work since we have large number of
projects and custm tasks in msbuild as well as wxs files. is there a way in
msbuild that I can schedule the wix compilation beforedropbuild and copy
this msi file to the binary folder?
Dmitry Berkovich wrote:
>
>
Hi,
Do you using Wix V3 and Votive?
If yes you have 2 options:
I) just install WiX on Team Build Server and you can compile solution that
have .wixproj project and it will be work.
II) If you don't want/can not install Wix on Team Build server write me
private email I will explain how you ca
10 matches
Mail list logo
