Problem TFS or VSTS builds that contain npm tasks take a very long time on a private build agent. As you can see in the

.Net, DevOps, Scrum, ALM, Clean Code, SharePoint, IoT, PowerShell
Problem TFS or VSTS builds that contain npm tasks take a very long time on a private build agent. As you can see in the
Docker is getting more and more popular. At Connect() 2016 Microsoft announced the Azure Web Apps on Linux that support docker. To build your containers
Disable source control Integration for all your nuget packages and resore them on the build server.
How to fix the error: ‘The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: Found value ‘aBcD’ with no corresponding key’ in Relese Management
The new build system in TFS or VSTS supports saving build definitions as templates. The problem is, that this only works inside a single TFS
Problem If you create an MSDeploy package for a SharePoint or O365 AddIn (a.k.a App) in a team build the package does not include all