title: Upgrading build server to Visual Studio 2013 has broken deployment process
body: <p>My build manager has been banging it's head on this for quite sometime.</p>
  
  <p>We were using Visual Studio 2012 Professional with MSDeploy.  Everything ran fine, we were able to do builds, Xml transforms, database deployments, web deployments, etc. to various environments.</p>
  
  <p>We recently upgraded our build server to Visual Studio 2013 Professional and pretty much all hell has broken loose.</p>
  
  <p>We get the following errors during our build process since upgrading:</p>
  
  <p>Error Code: ERROR_EXCEPTION_WHILE_CREATING_OBJECT</p>
  
  <p>More Information: Object of type 'manifest' and path 'C:\Builds\90\Code\Staging - Project\Binaries\Website Deployment\Project.Web.manifest' cannot be created.  Learn more at: <a href="http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT" rel="nofollow">http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXCEPTION_WHILE_CREATING_OBJECT</a>.</p>
  
  <p>Error: One or more entries in the manifest 'sitemanifest' are not valid.</p>
  
  <p>Error Code: FileOrFolderNotFound</p>
  
  <p>More Information: Could not find file 'C:\Builds\90\Code\Staging - Project\Binaries\Website Deployment\Project.Web'.  Learn more at: <a href="http://go.microsoft.com/fwlink/?LinkId=221672#FileOrFolderNotFound" rel="nofollow">http://go.microsoft.com/fwlink/?LinkId=221672#FileOrFolderNotFound</a>.</p>
  
  <p>Error count: 1.</p>
  
  <p>We have done everything possible to fix this issue.  We have tried everything to get this building again.  Even updating the project .prj file itself to point back to older .targets v10.0 from v12.0.</p>
  
  <p>When we do "change" targets, it give us this new error:</p>
  
  <p>C:\Builds\90\Code\Staging - Project\Sources\Project.Web\Project.Web.csproj (3290): The "TransformXml" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with  in the project file, or in the *.tasks files located in the "C:\Windows\Microsoft.NET\Framework64\v4.0.30319" directory.</p>
  
  <p>So it seems Visual Studio 2013 has modified something pretty significant in our environment to cause these errors during our Deployment process (the verbose log indicates that everything is building, just not deploying correctly).</p>
  
  <p>Any help would be awesome!</p>