Note that there are some explanatory texts on larger screens.

plurals
  1. POCopy Failed during post-build process
    primarykey
    data
    text
    <p>I am writing an ASP.NET web application using Visual Studio 2008. The project is mostly unchanged from the default empty project that Visual Studio provides, except for:</p> <ul> <li>In Properties->Build->Output, "XML documentation file" is checked and set to "bin\MyProject.XML"</li> <li>In Properties->Build Events, "Post-build event command line:" is set to <code>copy /y "$(TargetDir)$(TargetName).XML" "C:\TEMP\"</code></li> </ul> <p>When I build the project for the first time, or rebuild, the build process completes successfully. If I try to build any time after that, however, the build process fails with this message:</p> <pre><code>------ Build started: Project: MyProject, Configuration: Debug Any CPU ------ MyProject -&gt; C:\Projects\MyProject\MyProject\bin\MyProject.dll copy /y "C:\Projects\MyProject\MyProject\bin\MyProject.XML" "C:\TEMP\" The system cannot find the file specified. c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: The command "copy /y "C:\Projects\MyProject\MyProject\bin\MyProject.XML" "C:\TEMP\"" exited with code 1. Done building project "MyProject.csproj" -- FAILED. ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ========== </code></pre> <p>I'm certain that the syntax is correct, because I can perform the post-build command in a command window:</p> <pre><code>C:\&gt;copy /y "C:\Projects\MyProject\MyProject\bin\MyProject.XML" "C:\TEMP\" 1 file(s) copied. </code></pre> <p>The command works when I do it manually, so why does it fail when it is part of the build process?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload