This week I wrote on the Nonlinear Digital blog a piece on DevOps metrics. The goal was to give organization’s 4 easy metrics that they can track to see whether or not the changes they are making to their tools and processes are improving their overall flow through development and operations teams.
Unfortunately, I find we often don’t take the time to measure our delivery flow and therefore have no idea whether the changes we are making are helping or hurting us.
Have a read and let me know what you think!
Recently I needed to get builds running in Visual Studio Online (VSO) that contained Team Development for Sitecore (TDS) projects. Since I cannot install the TDS software on the VSO build server, I needed another way to get these projects to compile with a VSO build definition.
The following blog post has very detailed instructions on how to change your TDS project to use Hedgehog DLLs and a license file within your source control and helped immensely:
The referenced post indicates that you should update a file named TDSLicence.config in order to provide your TDS licence key. This file does not exist by default, so you will need to create it. The file name is important! I accidentally created the file with the American spelling ‘TDSLicense.config’ and the build server was unable to validate the file. Hedgehog support helped me out by pointing out my typo, but also explained that version 5.1 and up will support both spelling variations.
With the releases of Sitecore 7.5 and Sitecore 8 in the last 6 months, there has been a lot of interest from clients in upgrading from their current 6.x versions to the latest and greatest Sitecore platform version. This upgrade process always entails an examination of the modules involved in a solution. Keystone for Sitecore is no different. If you change versions of Sitecore, you will likely need to change which version of the Keystone software you have installed in your build.
Continue reading “Keystone: Considerations when upgrading to Sitecore 7.5 or Sitecore 8”
I was recently working on some deployments that leveraged Team Development for Sitecore (TDS) projects and began receiving the following error on the build server:
C:\Program Files (x86)\MSBuild\12.0\bin\amd64\Microsoft.Common.CurrentVersion.targets (990): .NET Framework v3.5 Service Pack 1 was not found. In order to target ".NETFramework,Version=v2.0", .NET Framework v3.5 Service Pack 1 or later must be installed.
Local compilation with Visual Studio looked fine and the build server was able to complete successfully if I excluded the TDS projects from the build configuration. This pointed to a problem in the TDS projects themselves.
Further investigation yielded that this is a TargetFrameworkVersion issue within the XML of the TDS project files. In my scenario the project files had a value of:
If the build server only has the most recent .NET assemblies installed, it will not be able to compile this project. Luckily, there are 3 easy steps to fix this for any TDS project file:
- Open up the .scproj file for manual editing with your favourite text editor application.
- Change <TargetFrameworkVersion>v2.0</TargetFrameworkVersion> to <TargetFrameworkVersion>v4.5<TargetFrameworkVersion>
- Save the project file.
NOTE: You may have to repeat this multiple times within a single project file. I noticed that my particular TDS project had two instances of the TargetFrameworkVersion tag in the XML!