Script on running MSBuild via PowerShell. This ties up neatly with my previous post. $msbuild = "C:\Windows\Microsoft.Net\Framework\v4.0.30319\MSBuild.exe" $MsBuilExists = Test-Path $msbuild If ($MsBuilExists -ne $true) {write-host "msbuild does not exist at this location. Install Visual Studio 2015 (Community Edition should be adequate)"} $buildFile = $PSScriptRoot+"\BuildAllDBProjects.targets.xml" & $msbuild $buildFile
You will need client tools installed as part of your SQL Server installation or the dlls won’t be on your box. Either way just search for those dll names in “C:\Program Files (x86)\Microsoft SQL Server" and they will probably be found.
<Project ToolsVersion="4.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003"
DefaultTargets="Default">
<ItemGroup>
<ProjectReference Include=".\**\*.sln" Exclude=".\**\DBSolutionToIgnore.sln"/>
</ItemGroup>
<Target Name="Default">
<MSBuild Projects="@(ProjectReference)" Targets="Rebuild"/>
</Target>
</Project>
( Part 2 focuses on clearing out the SSISDB by creating new stored proc based on the one used by the maintenance job. If your Maintenance Job is taking hours to run, you need to check this out.)
When deploying our Ispacs through my builds, I’ve still been getting the intermittent “timeout” issues I first wrote about back in May, and this has been exacerbated by extra SSIS Projects added to the SSISDB catalog.
Way back in 2008, a post on the blogs.msdn site showed how to create a custom MSBuild task to associate changesets and work items only since the last successful build. Recently I needed to write this custom task myself, but for builds that were “PartiallySuccessful” as well as “Successful”, and was pleased to find such a complete target available. However as it is written for TFS 2008 it won’t work with TFS 2010 onwards. As the blog appears to be inactive now I’ve made the changes and put the code below. Hopefully anyone who needs it for TFS 2010 onwards can use the pingback to get here for the up to date code. The rest of the solution works fine.
I’m in a bit of a Property Function mood at the moment with our builds. We generate a GUID within our builds for an Id required in one of our config file and some more for our WiX installers. There’s two ways to create GUIDs. Which one you use really depends on what version of MSBuild you are using.
Not so long ago I posted about string manipulations in SQL. Seeing as I recently had to use the MSBuild property functions I thought it best to post a fairly advanced example of using the .Net property functions in MSBuild as most of the examples I have found online are useful to no one. The kind of example I am talking about is found on the MSDN page:
[code langauge=“csharp”]
$(ProjectOutputFolder.Substring(0,3))
How to: Use the Same Target in Multiple Project Files.
Further to my post yesterday about Importing projects in MSBuild, it’s worth having a quick read over the “Order of Evaluation” section to understand further that it is important where you import a project if you wish to set the properties and items of the imported project.(TL;DR -
Hello, you can probably tell from the title of this blog that I’ve had a frustrating morning trying to overcome a limitation in MSBuild when importing a project.
Today has seen the release of Visual Studio 2012 – Update 2 RTM. There have been severaliterations of Update 2 in the form of CTP. IN fact I think if I recall the CTP 4 was RTM for TFS 2012 but not for Visual Studio 2012. Regardless, the RTM is ready to download. You can get it via this link below, or when you boot up VS 2012 a new download should be available. If you missed out on Update 1 then it is installed as part of Update 2…
Today has seen the release of Visual Studio 2012 – Update 2 RTM. There have been severaliterations of Update 2 in the form of CTP. IN fact I think if I recall the CTP 4 was RTM for TFS 2012 but not for Visual Studio 2012. Regardless, the RTM is ready to download. You can get it via this link below, or when you boot up VS 2012 a new download should be available. If you missed out on Update 1 then it is installed as part of Update 2…
When releasing a new version of our software there are typically cube changes that have to be deployed. We have only one SSAS Solution but we deploy it many times for reasons I won’t go into here. Suffice to say that cube deployment and processing is by far the biggest task of any release due to the number of databases we deploy and size of the cubes. We have been able to automate much of the deployment thanks to the use of Powershell and MSBuild.