Software Developer/Manager and Agile enthusiast
I've been looking forward to the release of Visual Studio 2015 for a while now so as soon as the RTM version was ready I was downloading it immediately.
After installing, I came across an error related to the
assembly when I tried to debug any of my web-based projects, as below:
As it turns out, the reason for this error was not down to installing Visual Studio 2015 alone - it was also because I uninstalled Visual Studio 2013 from my machine beforehand (SSD space is at a premium on my laptop these days).
The uninstallation of VS2013 causes the removal of this assembly but a reference to it still remains in the web.config of the .NET framework you are targetting in your project (2.0, 3.5, 4.0 or 4.5 in either 32 or 64 bit), for example:
<add assembly="Microsoft.VisualStudio.Web.PageInspector.Loader, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
The solution is to remove the reference from the web.config of the .NET framework you are using for your project. For example, my project was 64-bit .NET 4.5 so I removed the reference from:
You can find the other framework directories in:
C:\Windows\Microsoft.NET\Framework\[.NET version]\Configfor 32-bit
C:\Windows\Microsoft.NET\Framework64\[.NET version]\Configfor 64-bit
You should now be good to go with VS2015...
A quick tip when unit testing async methods in Visual Studio 2013.
This post will describe the next steps to rolling out the use of agile to other projects, engaging the entire company in the process, and the important step of putting the customer at the heart of it all.
The previous post talked about using commonly agreed estimations to better plan the team’s work; this post will explain how you can start to engage the wider business by making progress through the work more visible.
Following on from the previous post about taking the first steps into using agile methods, this post will cover how you can progress to making better estimates for your project as a team.
In any business, changing deeply ingrained working practices can be a real challenge. As a developer you may want to employ agile working practices but meet resistance from other developers or managers in your company.