Blog moved to Medium

For a while now, I moved my blogging to Medium.

Recent posts:

• The good old asof clause in WIQL queries for Azure DevOps
• Looking forward to 2020
• TFS 2017.3 — certificate issues with Git clone command (https)
• Reconfigure agents to connect to a new public url for TFS
• Xpirit Innovation Days
• Xpirit Belgium – looking for new talent
• Azure DevOps and SonarCloud, better together — Block Pull Requests for every code violation!
• The start of Xpirit Belgium
• Exporting Financial Transactions for import to an accounting platform

Clean sources at queue time without build definition update

In the old xaml TFS build era there was an option which seemed to have disappeared with the arrival of the new build architecture: cleaning sources at queue time without a modification to the build definition.

After queuing the build from Visual Studio you had the option to navigate to the parameters tab where you could choose on the fly your preferred method of cleaning the workspace, without forcing an upfront update to the build definition.

Now, with the new build system, the queue dialog window has changed a bit and that specific option is not available anymore out-of-the-box. The “Clean” option in the build definition also seems to be limited to a fixed true/false value from the dropdown.

Luckily, the field can also hold a custom variable which has been defined in the variables section. Don’t forget to mark the custom variable as “settable at queue time”.

Queuing a new build will now nicely provide you the option to choose the non-default value.

Happy building!

5 years of Techorama

Only a few days ago we celebrated 5 years of Techorama in Belgium and I wanted to take the time to reflect a bit on what we have realized in those 5 years.

Why Techorama?

When we (Gill, Kevin & myself) started preparing for the first edition of Techorama, the main goal really was to provide an alternative for the old TechDays conference which was organized by Microsoft in Belgium. At that time we were already heavily involved in community events via user groups and the yearly Community Day event … and we thought why not bundle our efforts somehow to come up with a new event as a potential replacement for TechDays.

It was more an instant reaction to the rumors that Microsoft wasn’t planning TechDays anymore in 2014. We all have been invited as speakers to DevDays/TechDays in various years and we couldn’t imagine a year without a (bigger) conference in Belgium where we could also learn from international speakers. With the final blessing and partner support from Microsoft Belgium for year 1 we decided to setup a new company and dive into the new world of event management.

How Techorama?

To start our private company we needed some cash/capital and the initial personal investment we made was also closely related to the commitment towards each other and the future success of Techorama. We wanted to go for the bootstrap startup model. The first 4 years we agreed to keep all earnings inside the company and invest year after year in the Techorama conference experience for all our stakeholders: attendees, partners and speakers.

Some of the (simple) principles we adopted from the start:

• No salary
• Don’t outsource work you can do yourself
• Hire true professionals for work you do not master yourself
• Invest time/effort in stuff which will be crucial for the long term success of Techorama
• Automate as much as possible in things which are not the core business
• Be responsive to any question from our stakeholders
• Nothing is impossible. Fail fast and try again. There will always be a solution!
• No concession on quality
• There is no status quo

Bootstrapping a new business can be hard. We were lucky to have an income from our other job and in some way we managed to organize all work for Techorama in our spare time (after hours + weekend). It hasn’t been easy for sure to find the right balance between our full-time jobs and our personal life. The people who know us a bit more will realize that all three of us have quite a different personality/character but we share some important key values to run a business together. We have proven to be compatible. We respect and trust each other as a partner and try to inspire each other to go the extra mile.

It’s only since last year that we introduced the official (paid) Techorama working days where we come together during business working hours (9AM – 5 PM). Upfront we plan about 2 of these working days a month and decide last-minute where to work from and seeing each other face-to-face. This can be our home or a meeting room we rent. Unfinished work for Techorama is taken care of in our spare time.

What Techorama?

Our vision for Techorama has always been to provide a premium conference experience where the focus is not only the content and the sessions. We have been to many different international conferences and we know what we like as an attendee/speaker. The experience is our cornerstone and we try to surprise with little details to make a substantial difference.

So cool! Our Tobian Yannick received a gift box from @TechoramaBE because he’s joining them for the fifth year in a row! #timetocelebrate #happy #techorama #countdown #nextweek pic.twitter.com/y3suQy2rsB

— Tobania (@Tobania_eu) May 15, 2018

https://platform.twitter.com/widgets.js

The last couple of years this modus operandi has also been picked up by our partners who add extra entertainment to their presence.

To convince our attendees to buy a ticket for Techorama, it’s primarily the content and the quality of speakers that plays an important role. For that reason we only contact/select speakers which are experts in their field, without going in a pure marketing direction to promote products/services.

Anyone who has been multiple times at Techorama will notice that we do not deliver a copy-paste experience. Every edition is different and we keep improving what can be improved. However we always remain faithful to a movie theatre venue with big screens, comfortable seats and exquisite food.

Check out the amazing food at #TechoramaBE pic.twitter.com/RNKBpCWCG0

— Pinal Dave (@pinaldave) May 23, 2018

https://platform.twitter.com/widgets.js

Who Techorama?

It goes without saying that for organizing Techorama a lot of people are involved and we are lucky and thankful to be surrounded by an exceptional dedicated team of volunteers from the local community in Belgium. Looking back at their efforts over the last couple of years, I find it interesting to see that everyone in the team has a (different) personal set of skills which contributes to the overall success of Techorama. Without these people, no Techorama! A big thank you to Andy, Ben, Jens, Jordi, Jorg, Karim, Kenny, Lindsey, Maarten, Mathias, Mike, Nico, Thomas, Tom and Wesley.

The evolution towards 1500 attendees

Growing from 500 attendees up to 1500 attendees has been an interesting challenge with a lot of important choices. Moving from Utopolis (Mechelen) to Kinepolis (Antwerp) was one of these choices which was necessary to bring our conference to the next level. Starting with 6 parallel breakout sessions, we now almost doubled with 11 parallel breakout sessions and have about 100 speakers.

Love this speakers room #Techorama thanks @TechoramaBE for taking such a good care of us. #mvpbuzz pic.twitter.com/EyT0EOwoyS

— Vincent Biret (@baywet) May 23, 2018

https://platform.twitter.com/widgets.js

We also evolved to not be the developer-only conference anymore by providing more IT Pro and Data related sessions. We noticed lots of differences in planning a show for 1500 people instead of 500 people. It required us to rethink our approach and planning to overcome the growing amount of work.

Each year we also noticed the increasing interest from other countries for our yearly conference. For Techorama 2018 we had attendees coming from 13 different countries: Belgium, The Netherlands, Norway, Denmark, Germany, Switzerland, Italy, Japan, Luxembourg, Poland, Romania, England and the USA.

What’s next?

The feedback in the past years from all our stakeholders (speakers, partners and attendees) has been very positive and we have been working hard to make it a long-term success by listening to all our customers. Today, it’s fair to say we kind of developed a business from our hobby and passion. As long as it feels we are not forced into another mandatory edition of Techorama, we will keep continuing what we are doing. Our first milestone has been achieved: creating a yearly international IT conference in Belgium with a premium experience for partners, speakers and attendees. Our next goal is to provide the same experience with organizing the first Techorama in the Netherlands (https://techorama.nl/).

We have a few other ideas up our sleeve but they are not ready yet for publication. Stay tuned for the next years. Our journey is not over yet!

A final thank you to all our partners and speakers for the continued support!

Generating Azure (VSALM) VMs from a specialized vhd file

From time to time I need to review how I run some of my Sparkles ALM workshops and make sure I can run a number of hands-on TFS exercises for the attendees. Doing demos is great to show what the possibilities are of an integrated ALM/DevOps platform, but nothing beats doing exercises yourself via the keyboard.

A long time ago I prepared exercises myself and this took quite a bit of effort, especially if you wanted to have some existing data in TFS to play with. When Brian Keller came up with a full-blown Visual Studio ALM virtual machine, I quickly realized I had to move into that direction. In the beginning (TFS 2010 timeframe) I paid for a big hosted server on the Internet where I could run a number of VMs via Hyper-V, but this was also very time-consuming and error-prone to have it up-and-running for my workshops.

Enter the cloud … Microsoft Azure! A perfect fit right? Upload vhd, create an image and ready for VM creation!

Well, I will save you all the details but in the past I managed to get it working after overcoming lots of different obstacles and it remained a very manual process … but it worked.

With the release of the new Visual Studio ALM VM for TFS 2018, I decided to have another go at it (what else to do during your Christmas holidays?) and script my way into having automated fresh VMs in Azure. First I failed a number of times creating a working VM image for TFS and providing a custom image for Azure Dev/Test Labs. The problem here might have been that creating the general image (sysprep instructions) kills the SQL connection for TFS. In the end I decided to abandon this approach and chose to upload a specialized vhd file to Azure and create VMs from that point. Many thanks to Sachin Hridayraj from Microsoft to provide me an already sanitized vhd file for upload to my Azure subscription. Sachin runs the ALM/DevOps Hands-On-Labs at https://almvm.azurewebsites.net/.

The Microsoft ALM/DevOps Hands-On-Labs is a set of self-paced labs based on Visual Studio Team Foundation Server and Visual Studio Team Services. Evaluating your next DevOps toolchain? Want to go deep and learn how you can implement modern DevOps practices with Visual Studio, Team Services and Azure? If you said yes to any of these questions, then this VM and Hands-on-labs are what you are looking for.

My PowerShell script to create VMs based on this uploaded vhd file can be consulted on GitHubGist. It will allow you to create a number of VMs based on the original VSALM vhd file provided at https://almvm.azurewebsites.net/. Be aware of some limitations (for example: number of cores) linked to your Azure subscriptions which might block you to generate extra VMs.

Hopefully in the (near) future I might move this one final step forward to create new VMs on the fly from Azure Dev/Test Labs.

Rename TFS Team Project Collection databases

When doing TFS migrations I’m often faced with mismatches between the name of the Team Project Collection and the underlying database file name. Instead of keeping track of which TPC is linked with a specific database file name, I recommend to keep the names aligned to avoid confusion.

How to do this?

First, make sure you have a valid backup of the complete TFS environment. The easiest way is to enable a built-in TFS backup plan.

• Detach the Team Project Collection via the TFS Administration Console

• Detach the matching SQL Server database from SQL Management Studio

• Rename the underlying database (.mdf) file to match the desired name for the Team Project Collection (prefix with Tfs_).
• Attach the SQL database via the renamed .mdf file. A new log file database (.ldf) will automatically be created. You can remove the old .ldf file.

• Attach the renamed database as a Team Project Collection via the TFS Administration Console and apply the desired Team Project Collection name (without prefix Tfs_).

Done!

Update appsettings.json at deploy time with VSTS Release Management

Lately I have to deal more with .NET Core Web Applications to setup build and release definitions in VSTS. What always comes up is how to deal with specific application settings which must me updated for a specific environment.

I have always been a big advocate of making a clear separation between build and release. The build should simply generate a generic package while the release should pick up the package and deploy it to any possible environment. At deployment time the specific enviroment values should be injected. Web Deploy has been the obvious tool in the past to make this happen with the capability to update the generated setparameters.xml file in a deployment action which injected the environment values into the web.config file.

Now with .NET Core and the typical appsettings.json file, it has become really easy in VSTS to inject custom values into the appsettings.json file.

Example of appsettings.json file in my solution:

Imagine that you would want to replace the values for the different settings (as from line 8). Note that it will also be possible to replace the values in the “Administrators” array.

First, you will need to create a build in VSTS which produces the deployment zip package (via dotnet publish command).

The VSTS release definition will link to the build output and you can use the built-in release task “Azure App Service Deploy” to deploy the build output to an Azure App Service.

The “File Transformation” section in the release task offers the possibility to define the JSON variable substitution. You will need to provide the file name from the root and the environment values (pay attention to the format of the variable names) can be set for the “DEV” environment.

Doing a file lookup from the console in the Azure Portal after deployment shows the result of the appsettings file.

Simple solutions are always the best solutions!

Refresh git remote branches in Visual Studio

Visual Studio doesn’t always refresh the git remote/published branches in the Branches View.

My solution to force a sync in Visual Studio is calling the git remote “prune” command (https://git-scm.com/docs/git-remote). This command will immediately detect new remote branches or remove the “stale” branches. Instant update in Visual Studio.

Migrate inline images to VSTS

Lately I have been planning a number of migrations to move small/big companies from TFS on-premises to Visual Studio Team Services (VSTS).

There are a number of options to migrate data from TFS to VSTS, but option 3 [high-fidelity database migration] is unfortunately not yet available. So, most of the time I still use custom/third-party tooling to perform the migration which is not always straightforward and may be very time-consuming.

One serious issue that popped up in a migration towards VSTS (using the TFS Integration Tools), was that the inline images in the Description field (or other html fields) of migrated work items were not properly migrated. The inline images are actually still referring to the old TFS on-premises environment because the html value of the Description field contains an <img> element with a source set to http://<tfs-on-prem>:8080/tfs/<tpc>/workitemtracking/v1.0/attachfilehandler.ashx?filenameguid=<guid>&filename=<filename>.png.

As a result, all inline images are only stored in the old TFS environment and they have not been uploaded to VSTS. The html value of the Description field has been migrated as-is. Initially you might not notice this after the migration of the selected work items because as long as the old TFS environment is still available, the inline image will be displayed. But what if the old TFS environment has been archived/destroyed?

To correct this and to upload the original images to VSTS, I have written some code (TFS API) to loop over the VSTS work items to detect image links to the old TFS environment. Using the source link of the original image, I can download the image to my local disk and upload it as an attachment to the VSTS work item. Finally, I’m replacing the original image source link with the new VSTS image link. Good to know is that once in-line images are detected inside the html field, those images are stored on the server and the temporary image file attachments may be deleted as well.

 

Migrating TFVC (TFS on-premises) to Git (VSTS)

In the last couple of months I do get more requests to move TFVC version control history to a git repository in Visual Studio Team Services (VSTS). The migration from TFVC to TFVC is at the moment possible via the TFS Integration Tools and is not that straightforward to accomplish. Migrating to a git repository is much simpler and is certainly the way to go if you were already planning to adopt git in the future. The migration can be done via Git-TF which is a set of cross-platform command-line tools that facilitate sharing of changes between Team Foundation Server, Visual Studio Team Services and Git.

What do you need to get started?

• Download git via https://git-scm.com/downloads
• Download and extract Git-Tf to your computer
• Add the extracted git-tf path to the system environment variable “path”
• Create a new “git” Team Project in VSTS

Migration Steps:

• Open a command-line prompt and navigate to a directory where you want to host the local git repository
• Call git-tf clone to push all TFS changeset info from TFVC to a new local git repo. The first argument is the Team Project Collection url. You pass the TF version control path to the exact branch in the second argument and you end the command with the “deep” flag to ensure that the full history of the branch is moved into separate commits in the git repo. Pass your credentials to connect to TFS and execute the command.

• Once you have a local git repository it’s easy to push it towards an empty central VSTS git repository. First use the git remote add command to link your local git repo to the remote “origin” and afterwards you can push all changes via git push.

Navigate to the Code Hub in your VSTS Team Project and you should see all code history inside the git repo. What’s a big plus is that the original changeset date/time stamps are now part of the git commit info.

Work Item Query via TFS API and the dayPrecision parameter

By default TFS doesn’t pay attention to the time part in work item queries when comparing datetime values. If you want to launch a query and you need to take into account the exact timestamp, you must switch off the dayPrecision parameter in the Query constructor.

using the dayPrecision parameter in the Query constructor

MSDN documentation: https://msdn.microsoft.com/en-us/library/bb133075(v=vs.120).aspx

Mystery resolved!