There have been some requests for more information about the areas I convered in my presentation at the Black Marble Tech Update 2016 that we held last week. I could send out slides, but I think it is far more useful to point you at the ‘live’ resource on the Internet. The key reason for this is that the whole of the Visual Studio family is now being released at a ‘cloud cadence’ i....
As I discovered during my BlogEngine upgrade, there is an effort within the project team to focus the codebase on three possible usage models on any given BlogEngine server instance: Single blog with a user – a personal blog (default) Single blog with many users – a team/company blog Many blogs each with a single user – a set of related blogs that can be agregated togther I needed the third option, problem was in its history our blog has been both of the other two types, so I have multiple user accounts for each blogs, and login usernames are repeated between individual blogs on the server....
I have just completed the upgrade of this blog server to the new release 3.2 of BlogEngine.NET. I did a manual upgrade (as opposed to the automated built in upgrade) as I needed to make a few changes from the default settings. The process I used followed the upgrade process document Downloaded the latest release and unzip the folder Run the SQL upgrade script (in /setup/sqlserver folder), this adds some new DB constraints Created a IIS web site using the new release Copied in the sample web....
If you want to run CodeUI tests as part of a build you need to make sure the device running the test has access to the UI, for remote VMs this means having a logged in session open and the build/test agent running interactivally. Problem is what happens when you disconnect the session. UNless you manage it you will get the error Automation engine is unable to playback the test because it is not able to interact with the desktop....
My primary blog editor has been Microsoft Live Writer for years, but it has always been a pain to install via Windows Essentials (as I don’t want the rest of the product), also I was never able to find the right version when I rebuilt a PC. This was not helped by the fact there has been no development of the product for years, so I struggled to remember what year version I really needed (last one was 2012 by the way)....
We are currently working on updating a Windows 8 application to be a Windows 10 Universal application. This has caused a few problem on a TFS vNext automated build box. The revised solution builds fine of the developers box and fine on the build VM if opened in Visual Studio, but fails if built via the VSTS vNext build CI MSBuild process showing loads of references missing. Turns out the issue was due to Nuget versions....
Updated 10 Aug 2016 - Revised for Win10 anniversary build 1607 I have posted in the past about using a DD-WRT virtual router to bridge between local VMs on my development PC and the outside world With the recent changes in HyperV on Windows 10 and Server 2016 we have an alternative as discussed by Thomas Maurer in his post (pre Win10 anniversary build 1607) or this post (post Win10 anniversary build 1607)....
I have been using a Band 2 for a couple of weeks now as opposed to my original Band. The major thing I have noticed is I don’t notice it on my wrist. It feels just like a watch. The old one, though not too bad did feel a bit lumpy, banging on the wrist. So that is an improvement, also it looks less like I am a prisoner with a tracker on day release....
Vijay in the Microsoft Release Management product group has provided a nice post on the various methods you can use to migrate from the earlier versions of Release management to the new one in Visual Studio Team Services. An area where you will find the biggest change in technology is when moving from on premises agent based releases to the new VSTS PowerShell based system. To help in this process the ALM Rangers have produced a command line tool to migrate assets from RM server to VSTS, it exports all your activities as PowerShell scripts that are easy to re-use in a vNext Release Management process, or in Visual Studio Team Services’ Release tooling....
Many of the major new features of VSTS are delivered by the new marketplace and extension model, such as code search and package management. However, did you realise that this new way of adding functionality to VSTS is open to you too, not just to Microsoft? To see what can be done why not have a look at the Visual Studio Team Services Extensions from the ALM Rangers