Email me when the day comes that a file unintentionally disappears from the 
installer and it goes unnoticed. :-)   Trust me, I've been doing build and 
install for 15 years and it will happen.  


The problem you mention is easily solved by putting the responsibility on 
the developer to make sure that he's "done done" and tests the installer 
and related functionality change on a clean machine.  Making it an 
automagical process just gives the developer more excuses as to why it's 
not his fault when it doesn't work.


Also are you doing major upgrades or minor upgrades?  How about patches?

----------------------------------------

From: "David Rickard (USA)" <davri...@microsoft.com>

Sent: Wednesday, September 21, 2011 1:44 PM

To: "chr...@iswix.com" <chr...@iswix.com>, "General discussion for Windows 
Installer XML toolset." <wix-users@lists.sourceforge.net>

Subject: RE: [WiX-users] Best way to invoke Wix from a TFS build workflow?

Thanks for the advice.
 
Though our devs work with the raw built files and our TFS builds clearly 
identify build breaks. Installer issues (like someone adding a file to the 
solution but forgetting to add it to the installer) would be at risk of 
going unnoticed.
 
From: Christopher Painter [mailto:chr...@iswix.com] 

Sent: Wednesday, September 21, 2011 10:48 AM

To: David Rickard (USA); General discussion for Windows Installer XML 
toolset.

Subject: RE: [WiX-users] Best way to invoke Wix from a TFS build workflow?
 
Open the solution up and click properties on the merge module project.  Go 
to the build events tab then type your command into the pre-build event 
command line.


I still wouldn't do it though.  This type of dynamic authoring frequently 
masks up stream problems.  What should have been a build break will end up 
being a runtime break.
 

----------------------------------------

From: "David Rickard (USA)" <davri...@microsoft.com>

Sent: Wednesday, September 21, 2011 12:44 PM

To: "chr...@deploymentengineering.com" <chr...@deploymentengineering.com>, 
"General discussion for Windows Installer XML toolset." 
<wix-users@lists.sourceforge.net>

Subject: RE: [WiX-users] Best way to invoke Wix from a TFS build workflow?


Alright. In this case how would you run a program to add all the files in a 
given directory to the MSI? Before we had an EXE that generated a merge 
module of files based on a directory. Could this hook in somehow?


-----Original Message-----

From: Christopher Painter [mailto:chr...@deploymentengineering.com] 

Sent: Tuesday, September 20, 2011 4:09 PM

To: General discussion for Windows Installer XML toolset.; 
wix-users@lists.sourceforge.net

Subject: Re: [WiX-users] Best way to invoke Wix from a TFS build workflow?


The simplest way is to use Votive to generate a .SLN / .WIXPROJ and then 
add the sln configuration | platform to to the build parameters in the 
build definition. You shouldn't have to do any customizations in workflow 

as the Default Template will work out of the box. Passing a 

ProductVersion property takes a little bit more work on the msbuild side ( 
build parameters and preprocessor definitions in the wixproj and wixs ) but 
it doesn't require any workflow changes.


----------------------------------------


From: "David Rickard (USA)" <davri...@microsoft.com>


Sent: Tuesday, September 20, 2011 5:11 PM


To: "wix-users@lists.sourceforge.net" <wix-users@lists.sourceforge.net>


Subject: [WiX-users] Best way to invoke Wix from a TFS build workflow?


I need to build some MSIs with Wix during our TFS build. Our current TFS 
build is using the Windows Workflow XAML files to declare the build logic. 


What's the best way to invoke Wix from there? Directly invoking the process 
from an activity? Going down to a powershell script and calling it from 
there? Are there any custom Wix activities to use?


----------------------------------------------------------------------------


--


All the data continuously generated in your IT infrastructure contains a


definitive record of customers, application performance, security


threats, fraudulent activity and more. Splunk takes this data and makes


sense of it. Business sense. IT sense. Common sense.


http://p.sf.net/sfu/splunk-d2dcopy1


_______________________________________________


WiX-users mailing list


WiX-users@lists.sourceforge.net


https://lists.sourceforge.net/lists/listinfo/wix-users


----------------------------------------------------------------------------
--

All the data continuously generated in your IT infrastructure contains a 
definitive record of customers, application performance, security threats, 
fraudulent activity and more. Splunk takes this data and makes sense of it. 
Business sense. IT sense. Common sense.

http://p.sf.net/sfu/splunk-d2dcopy1

_______________________________________________

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to