Uncategorised

If you are using a parameters.xml file to set value with MSDeploy I have just found a gotcha. You need some value in the web.config file, not just an empty XML tag, else the replacement fails. So to explain… I had the following parameters.xml file, and use Release Management to replace the __TAG__ values at deployment time. <parameters> <parameter name="Domain" description="Please enter the name of the domain" defaultvalue="\_\_Domain\_\_" tags=""> <parameterentry kind="XmlFile" scope="\\web....

When you using MSdeploy you should create a parameters.xml file that exposes your web.config settings at the time of installation. This enables good deployment habits, build the product one and then set system specific values using deployment tools. The problem is that this parameters.xml file is a pain to write, it is a series of XML blocks that contain XPath to find the entries to replace, typo’s are easy to introduce....

Mid May is a busy time for me presenting-wise: On the 12th/13th I am presenting at Techorama in Belgium And on the 14th I will be presenting at a Microsoft/GreyMatter event at Microsoft’s Reading office. And after that there are also the Black Marble Re:Build and Re:Ignite events. I am sure I will be involved at those, but we have to wait for a couple of week until after Build and Ignite to find out what we will be talking about....

I have worn a Polar s610 heart rate monitor as my watch for years (probably 15+), as I write it needs another battery swap, which means sending it to Polar, something I have done a couple of times in the past for servicing The batteries in the watch last 5 years or so, in the associated heart rate monitor strap maybe a bit more depending on usage. The point is I am used to having a device that ‘can’ give heart rate information, it seems normal, but I do need to remember to put on the heart rate strap, something I would only usually do for a race or specific training set....

Updated 6 Feb 2016 - See the newer post about the new vNext build task I have written to do the same job Virtually any automated build will require some customisation beyond a basic compile. So as part of my upcoming Techorama session on TFS 2015 vNext build I need a demo of using a custom script as part of the build process. Two common customisations we use are version stamping of assemblies and running code analysis tools....

All change again on Visual Studio SKU licensing, have a look at the blog post on new SKUs for the 2015 release and also the 2015 product site. Basically it is a simplification. You can find the detailed feature break down on the comparison site

I have been preparing for my Techorama session on TFS vNext build. One of the demo’s I am planning is to use the Node based cross platform build agent to build something on a Linux VM. Turns out this takes a few undocumented steps to get this going with the CTP of TFS 2015 The process I followed was: I installed a Mint 17 VM On the VM, I installed the Node VSOAgent as detailed in the npm documentation (or I could have built it from from source from GitHub to get the bleeding edge version) I created a new agent instance...

Black Marble are hosting, at our offices, a Microsoft event on the 18th March on ALM with Visual Studio & TFS 2013. This is a repeat of the sell out event we hosted in the autumn. For details of the event and registration see the booking site

A couple of weeks ago I presented on DSC and Release Management as part of the Microsoft UK TechDays Online 2015 event. All the sessions from this three day event are now available on demand at TechDays Online 2015 on-demand sessions. You do seem to have to register/login to see the content, so I can’t deep link to my session, but browsing the catalogue is a good idea there are some great sessions

We use my TFS Alerts DSL to perform tasks when our TFS build complete, one of these is a job to increment the minor version number and reset the version start date (the value that generates third field – days since a point in time) if a build is set to the quality ‘release’ e.g. 1.2.99.[unique build id] where 99 is the days count since some past date could change to 1....