File Path of greater than 260 characters with TFS Automated builds

Working with TFS automated builds for BizTalk I have started to run into the TFS / MSBuild file path length restrictions (no, I don’t understand in modern operating system why the build process has a file path limit) and have tried several ways to reduce the path length, with varying degrees of success, this week I discovered one way to help reduce the path length without compromising the TFS Automated build process and I would like to share it with you.

Example of the default location for the source on a build server, I have highlighted one of the longer examples:

In the TFS build Agent there is a variable that controls the start of the source location on the build server, it is called Working Directory

The default value for this is:

$(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionPath)

In the build server I have this is:

C:\Builds\5\Mexia\BizTalkDemo_buildv3

The last part of this is the source tree path and the name of the build, which are typically much longer than this example.

To reduce this I found that we can change $(BuildDefinitionPath) to $(BuildDefinitionId)

$(SystemDrive)\Builds\$(BuildAgentId)\$(BuildDefinitionId)

This changes the starting path to:

C:\Builds\5\15

This is reduce the path by 13 characters, but if your source tree path and build definition name are a typical size this may reduce the path by almost 100 characters, without compromising any part of the build process.

The previous list of files now looks like this:

I hope this tip helps solve your automated build path lengths issues.

More …

Azure: Outbound throttling of VMs

When we create certain sized VMs, the NICs associated with them are throttled for
Outbound traffic. Here’s some numbers that were originally published from a little
while ago (may have changed since, but these give you a guide):

Specifications

Extra Small

Small

Medium

Large

Extra Large

CPU

1.0 GHz

1.6 GHz

2 X 1.6 GHz

4 X 1.6 GHz

8 X 1.6 GHz

Memory

768 MB

1.75 GB

3.5 GB

7 GB

14 GB

VM Local Storage

20 GB

225 GB

490 GB

1,000 GB

2,040 GB

Network I/O Performance

Low

Moderate

High

High

High

Allocated Bandwidth

5 Mbps

100 Mbps

200 Mbps

400 Mbps

800 Mbps

Blog Post by: Mick Badran

Join Me at Microsoft TechEd to Talk DevOps, Cloud Application Architecture

Join Me at Microsoft TechEd to Talk DevOps, Cloud Application Architecture

In a couple weeks, I’ll be invading Houston, TX to deliver a pair of sessions at Microsoft TechEd. This conference – one of the largest annual Microsoft events – focuses on technology available today for developers and IT professionals. I made a pair of proposals to this conference back in January (hoping to increase my […]
Blog Post by: Richard Seroter

How did we use our BizTalk360 7.2 release for team building activity?

The BizTalk360 team had grown considerably in the past few months. When you grow so quickly, it’s inevitable you’ll face some challenges around the processes in the company, the company culture, bringing everyone up to speed etc., – known more as the classic scalability issues. We thought it will be a good opportunity to capitalize […]

The post How did we use our BizTalk360 7.2 release for team building activity? appeared first on BizTalk360 Blog.

Blog Post by: Gokul Dhamodaran

Temporary Post Used For Theme Detection (33d6cbe8-5e27-424d-a286-5fc92356d33f – 3bfe001a-32de-4114-a6b4-4005b770f6d7)

This is a temporary post that was not deleted. Please delete this manually. (d96073bb-052b-4975-9da0-288f8bfe23e9 – 3bfe001a-32de-4114-a6b4-4005b770f6d7)

The post Temporary Post Used For Theme Detection (33d6cbe8-5e27-424d-a286-5fc92356d33f – 3bfe001a-32de-4114-a6b4-4005b770f6d7) appeared first on BizTalk360 Blog.

Blog Post by: Gokul Dhamodaran

BizTalk360 improved User Experience (UX) and User Interface (UI) in 7.2

One of the things we are very passionate in BizTalk360 is the user experience. That’s one of the reason we invested heavily last year moving from Silverlight based UI to modern HTML5 based single page interface. Out of the box BizTalk server comes with BizTalk admin console, a standard MMC based snap-in, which is15 years […]

The post BizTalk360 improved User Experience (UX) and User Interface (UI) in 7.2 appeared first on BizTalk360 Blog.

Blog Post by: Sriram Hariharan

ESB Toolkit Tip #1: Create a Custom Extender for an Itinerary Service

In an Itinerary Service you can use a Resolver for dynamically resolving endpoint information and BizTalk Maps. Most of the times when you create a custom Itinerary Service you want to transform or send your message but there are also cases that you want to do something else like logging or validating your message. In that case Resolvers are not useful because the properties and data that they return contain endpoint information and maps.
The Itinerary Designer in Visual Studio fortunately allows you to create custom extenders for Itinerary Service model elements that can be used to add properties to the property bag for use by Orchestration-based Itinerary Services. Through this you no longer need to use a Resolver to feed your Orchestration with dynamic data because you can set the properties directly on the Itinerary Service.

 

Figure 1. Itinerary with an Itinerary Service that uses a custom Extender.
 
Figure 2. Itinerary Service Properties.
 

 

See Also

For more information see: Creating a Custom Extender for an Orchestration-Based Itinerary Service