If you read my earlier blog post about a mysterious error from BTSTask you already know that I’m currently helping a customer with automated TFS 2008 builds for BizTalk 2009, if you haven’t read my earlier post here’s your chance.
Firstly you’ll have to setup some sort of build server and there’s at least 3 ways you can do this:
- Have the build server installed separate from the “build BizTalk server”
- Have the build server start a virtual snapshot of a “build BizTalk server”
- Have the build server installed on the “build BizTalk server”
I typically skip the first option because it usually end up in me having to write some kind of remote execution scripts (PSExec) or starting the scripts with timer jobs. Either way the overall build pattern turns out more complex than it needs to be or managing the build (yes you will be managing your builds) will be harder.
The second option would be the top choice for me if the customer has TFS 2010 and Lab Management in place. I know there are virtualization options for TFS 2008 but I’ve never user them myself.
So this leaves my with the option to have the “build BizTalk server” and the build server on the same box which makes it a lot easier.
Remember that you’ll need to install and configure the BizTalk server and remember to install/configure these options during the installation of the BizTalk server:
- Developer Tools and SDK
- Additional Software / Project Build Component, build component used by TFSBuild.
When the BizTalk server is installed and configured you’ll need to make/configure these options:
- The service account for TFSBuild need to be added to the local Administrators group, required to install/uninstall assemblies to the GAC.
- The service account for TFSBuild need to be added to the BizTalk Administrators group, required to use BTSTask operations.
As a common practice I always create a Hello World build type to test that my build server is working correctly before moving on with any advanced build patterns with automatic deploy for instance.
Hope you’ll enjoy this first part of the series!
2010-11-15 Script file updated
This blog post has been updated after feedback from my colleagues Markus Ahlstrand and Johan Leino, thanks you guys! The original blog post contained 1 error and needed 2 clarifications and 1 refinement, all updated content is highlighted below.
I’ve worked a lot with SharePoint development during the last 3 years and before SharePoint 2010 you could use Virtual PC to create your development environment. But as you might know a SharePoint 2010 development environment has to be on an x64-bit environment as described in this article “Setting up the Development Environment for SharePoint 2010…
So this left me with some alternatives:
- Install the bits on your own x64-machine.
- Use another virtualization platform such as Hyper-V, VMWare or VirtualBox that have support for x64 on my own x64-machine.
- Create a bootable VHD from Windows 7.
I chose the bootable VHD option because I love the feel of Windows 7 and the rich features that Windows 7 gives the end user. On the other side I need the flexibility to start my SharePoint 2010 box when I need that with (almost) no performance loss.
There’s a lot of blogs out there that describe how to create a bootable VHD and so I will not list them here but I will give you a nice automated head start (without MB’s of download).
In the linked CreateBootableVHD_v2.zip you will find two files:
- A machine running Windows 7 or Windows Server 2008 R2.
- Windows 7 or Windows Server 2008 R2 installation media or a Windows 7 or Windows Server 2008 R2 .wim image captured from a reference machine.
The following steps are provided with a “works on my box” guarantee.
Ex: .\CreateBootableVHD_v2.bat C:\VHD\W2k8.vhd 40000 FIXED X F:\sources\install.wim
To show an actual example here is a snapshot from my latest run:
After 30-60 minutes depending on the size of the VHD and your hardware you’ll have a new boot option.
Hope you enjoy the script.