[wix-users] Tricks and Tips on Automating Builds and Releases with VSTS Team Build 2015 and WiX

[Anna Flyam | Landtech]

Chris,
Thank you so very much!
I will follow your instructions.



*Anna Flyam*
*Software Engineer*
*Landtech Data Services*

[image: Landtech] <http://www.landtechdata.com/index.php>
Main O: (800)-835-1523 <%28800%294835-1523> | F: (561)-798-818
<%28561%294798-0818> |  E: Anna at Landtechdataservices.com
<Anna at landtechdataservices.com>
1460 Royal Palm Beach Blvd,
Royal Palm Beach, Florida 33411
www.landtechdata.com

On Fri, Jul 14, 2017 at 2:28 PM, Christopher Painter <chrpai at iswix.com>
wrote:

> For TFS I simply add the sln to the solutions to build list. For
> PowerShell I use the Invoke-MsBuild module like such:
>
>
>     # https://github.com/deadlydog/Invoke-MsBuild
>     Import-Module "$PSScriptRoot\Invoke-MsBuild"
>
>
>
>   # Version and build the installer
>     $slnFile = "$pwd\Installer\Installer.sln"
>     if(Test-Path $slnFile)
>     {
>     $buildResult = Invoke-MsBuild -Path $slnFile -MsBuildParameters
> "/t:Rebuild /p:Configuration=Release;Platform=Installer;
> MSIProductVersion=$buildNumber" -ShowBuildOutputInCurrentWindow
> -BuildLogDirectoryPath $pwd
>     if ($buildResult.BuildSucceeded -eq $false)
>     {
>         Write-Host "Installer Build Failed"
>         Exit -2
>     }
>     }
>
>
> For MSDOS BAT files I say:
>
> call build_one.bat "%CD%\Installer\Installer.sln" Installer
>
> where build_one.bat has:
>
> rem --------------------------------------------------------------------
> rem Set build path based on installed Visual Studio version
> rem --------------------------------------------------------------------
> @if exist "%ProgramFiles(x86)%\MSBuild\14.0\bin" (
> set "ms_build_path=%ProgramFiles(x86)%\MSBuild\14.0\bin"
> ) else (
> set "ms_build_path=%windir%\Microsoft.NET\Framework\v4.0.30319"
> )
>
>
> rem --------------------------------------------------------------------
> rem Only set the path once
> rem --------------------------------------------------------------------
> if not defined build_path_initialized (
> set "build_path_initialized=TRUE"
> set "path=%ms_build_path%;%path%"
> )
>
>
> msbuild %1 /t:Rebuild /p:Configuration=Release;Platform=%2
>
>
>
>
> ________________________________
> From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of
> Anna Flyam | Landtech <anna at landtechdataservices.com>
> Sent: Friday, July 14, 2017 9:55 AM
> To: WiX Toolset Users Mailing List
> Subject: Re: [wix-users] Tricks and Tips on Automating Builds and Releases
> with VSTS Team Build 2015 and WiX
>
> Are you using TFS/VSTS with this 3-rd party software? Does it generate
> msbuild script or a custom set of tasks (json files) that you can import to
> drive the process?
>
> Thank you so very much,
> Anna
>
> On Jul 13, 2017 5:26 PM, "Wheeler, Blaine (DSHS/DCS)" <
> BWheeler at dshs.wa.gov>
> wrote:
>
> > I have a similar world to yours.   We use VisualBuildPro from
> > www.kinook.com<http://www.kinook.com> to order, aggregate and trigger
> steps.   In effect it is
> Kinook Software - Automated software builds<http://www.kinook.com/>
> www.kinook.com
> Kinook - A Windows GUI for scripting build processes. Features macros,
> conditional build rules, windows registry tools, failure responses, project
> wizards, and vsmake ...
>
>
>
> > out build definition.
> >
> > -----Original Message-----
> > From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On
> Behalf
> > Of Anna Flyam | Landtech
> > Sent: Wednesday, July 12, 2017 12:41 PM
> > To: WiX Toolset Users Mailing List
> > Subject: [wix-users] Tricks and Tips on Automating Builds and Releases
> > with VSTS Team Build 2015 and WiX
> >
> > If every app is a .net application it's easy to create one build
> > definition that builds all the app, but it gets interesting if you need
> to
> > build/package/deploy VB6 legacy applications, .net solution, and WiX
> > solution.
> > We have 3 different build processes that get source code from 3 different
> > Team Projects in VS Version Control. One for .net apps, one for VB6
> legacy
> > applications, and one for Installer (includes WiX setup projects, Custom
> > Actions project, and the custom manged BA). When you have process that
> has
> > segregated elements, they somehow need to be brought together.
> >
> > Are you utilizing the REST APIs provided by VSTS within a Poweshell
> script
> > to create a Master build that calls other builds? Are there any good
> > samples?
> > Do you have tips and tricks that you can share on how to put it all
> > together using VSTS Team Build 2015?
> >
> > Thanks in advance,
> > Anna
> >
> > PS: We are refactoring a very large pre-MSI process and I can use your
> > advice in order to do it efficiently and avoid serious mistakes.
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>