Wrong package location when reusing a Release Management component
Whilst setting up a new agent based deployment pipeline in Release Management I decided I to reuse an existing component as it already had the correct package location set and correct transforms for the MSDeploy package. Basically this pipeline was a new copy of an existing website with different branding (css file etc.), but the same configuration options. I had just expected this work, but I kept getting ‘file not found’ errors when MSDeploy was run....