Whilst building a new TFS build agent VM using our standard scripts I hit a problem that SSDT projects would not build, but was fine on our existing agents. The error was C:Program Files (x86)MSBuildMicrosoftVisualStudiov12.0SSDTMicrosoft.Data.Tools.Schema.SqlTasks.targets (513): The “SqlBuildTask” task failed unexpectedly. System.MethodAccessException: Attempt by method ‘Microsoft.Data.Tools.Schema.Sql.Build.SqlTaskHost.OnCreateCustomSchemaData(System.String, System.Collections.Generic.Dictionary`2<System.String,System.String>)’ to access method ‘Microsoft.Data.Tools.Components.Diagnostics.SqlTracer.ShouldTrace(System.Diagnostics.TraceEventType)’ failed. The problem was fixed by doing an update via the Visual Studio > Tools > Extensions and Updates. Once this was completed the build was fine. ...

I posted a month or so ago about my ‘Experiences using a DD-WRT router with Hyper-V’, well I have been living with it over a month? How has it been going? Like the curate’s egg ‘good in parts’. It seems OK for while and then everything would get a bit slow to stop. Just as a reminder this is what I had ended up with In essence, a pair of virtual switches, one internal using DHCP on the DD-WRT virtual router, and a second one connected to an active external network (usually Ethernet, as DHCP with virtual switches and WIFI in Hyper-V seem a very hit and miss affair). ...

We use O365 to provide Lync messaging. So when I rebuilt my PC I thought I needed to re-install the client; so I logged into the O365 web site and selected the install option. Turns out this was a mistake. I had Office 2013 installed, so I already had the client, I just had not noticed. If you do install O365 Lync client (as well as Office 2013 one) you get file access errors reported with your outlook.ost files. If this occurs, just un-install the O376 client and use the one in Office 2013, the errors go away ...

There have been a load on announcements about TFS, VSO and Visual Studio in general in the past couple of week, mostly at the Connect() event. Just to touch on a few items Visual Studio and Team Foundation Server 2013 Update 4. The first public preview of Visual Studio 2015 and .NET 2015 The .NET Framework is going open source and cross platform Visual Studio Community 2013 – a new edition of Visual Studio that combines everything in all the Express products and adds extensibility support. Learn more… New improvements to Visual Studio Online Release Management as service on VSO If you have not had a chance to have look at these features try the videos of all the sessions on Channel9, the keynotes are a good place to start. Also look, as usual, at the various posts on Brian Harry’s Blog. It is time of rapid change in ALM tooling ...

Whilst getting integration tests running as part of a Release Management pipeline within Lab Management I hit a problem that TCM triggered tests failed as the tool claimed it could not access the TFS build drops location, and that no .TRX (test results) were being produced. This was strange as it used to work (the RM system had worked when it was 2013.2, seems to have started to be issue with 2013.3 and 2013.4, but this might be a coincidence) ...

Whilst over at the MVP Summit I had the chance to do a Scaled Agile Framework workshop. I am pleased to say I passed the assessment. Certainly has some interesting ideas in scaling Agile to larger teams working on a single product stream where a simple Scrum of Scrums is not enough.

I have been setting up some integration tests as part of a release pipeline. I am using TCM.EXE to trigger tests from the command line. Something along the lines TCM.exe run /create /title:"EventTests" /collection:"[http://myserver:8080/tfs](http://myserver:8080/tfs)” /teamproject:myteamproject /testenvironment:"Integration" /builddir:[\\serverDropsBuild\_1.0.226.1975”](//\serverDropsBuild_1.0.226.1975”) /include /planid:26989 /suiteid:27190 /configid:1 I kept getting the error ‘A test run must be created with at least one test case’ Strange thing was my test suite did contains a number of test, and they were marked as active. ...

I have a few old Visual Studio Online (VSO) accounts (dating back to TFSPreview.com days). We use them to collaborate with third parties, it was long overdue that I tidied them up; as a problem historically has been that all access to VSO has been using a Microsoft Accounts (LiveID, MSA), these are hard to police, especially if users mix personal and business ones. The solution is to link your VSO instance to an Azure Active Directory (AAD). This means that only users listed in the AAD can connect to the VSO instance. As this AAD can be federated to an on-prem company AD it means that the VSO users can be either ...

Whilst repaving my Lenovo W520 I had some issues with video cards. During the initial setup of Windows the PC hung. I rebooted, re-enabled in the BIOS the problematic video card and I thought all was OK. The installation appeared to pickup where it left off. However, I started to get some very strange problems. My LiveID settings did not sync from my other Windows 8.1 devices I could not change my profile picture I could not change my desktop background I could not change my screen saver And most importantly Windows Update would not run I found a few posts that said all of these problems could be seen when Windows was activated, but that was not the issue for me. It showed as being activated, changing the product key had no effect. ...

Updated 19th Nov 2014 Every few months I find a PC needs to be re-paved – just too much beta code has accumulated. I reached this point again on my main 4 year old Lenovo W520 recently. Yes it is getting on a bit in computer years but it does the job; the keyboard is far nicer than the W530 or W540’s we have and until an ultrabook is shipped with 16Gb of memory (I need local VMs, too many places I go to don’t allow me to get to VMs on Azure) I am keeping it. ...