I have a project with a post build event:
copy $(ProjectDir)DbVerse\Lunaverse.DbVerse.*.exe $(TargetDir)
It works fine every time on my machine. I have a new developer who always gets the "exited with code 1" error. I had her run the same command in a DOS prompt, and it worked fine. What could be causing this? Is there any way to get to the real error?
We are both using Visual Studio 2008.
The one with the "Pings" helped me... but may be explained a little better...
For me the solution was to change:
copy $(TargetDir)$(TargetName).* $(SolutionDir)bin
to this:
copy "$(TargetDir)$(TargetName).*" "$(SolutionDir)bin"
Hope it works for you. :-)
My reason for the Code 1 was that the target folder was read only. Hope this helps someone! I had a post build event to do a copy from one directory to another and the destination was read only. So I just went and unchecked the read-only attribute on the directory and all its subdirectories! Just make sure that its a directory that's safe to do so!
Get process monitor from SysInternals set it up to watch for the Lunaverse.DbVerse (on the Path field) look at the operation result. It should be obvious from there what went wrong
As a matter of good practice I suggest you replace the post build event with a MS Build File Copy task.
Yet another answer ...
In my case I had a Visual Studio 2017 project targeting both .Net Standard 1.3 and .Net Framework 2.0. This was specified in the .csproj file like this:
<TargetFrameworks>netstandard1.3;net20</TargetFrameworks>
I also had a post-build event command line like this:
copy "E:\Yacks\YacksCore\YacksCore\bin\net20\Merlinia.YacksCore.dll" "E:\Merlinia\Trunk-Debug\Shared Bin\"
In other words I was trying to copy the .Net Framework .dll produced by the build to an alternative location.
This was failing with this error when I did a Rebuild:
MSB3073 The command "copy "E:\Yacks\YacksCore\YacksCore\bin\net20\Merlinia.YacksCore.dll" "E:\Merlinia\Trunk-Debug\Shared Bin\"" exited with code 1.
After much frustration I finally determined that what was happening was that Rebuild deleted all of the output files, then did the build for .Net Standard 1.3, then tried to run the post-build event command line, which failed because the file to be copied wasn't built yet.
So the solution was to change the order of building, i.e., build for .Net Framework 2.0 first, then for .Net Standard 1.3.
<TargetFrameworks>net20;netstandard1.3</TargetFrameworks>
This now works, with the minor glitch that the post-build event command line is being run twice, so the file is copied twice.
In my case I had to cd (change directory) before calling the bat file, because inside the bat file was a copy operation that specified relative paths.
:: Copy file
cd "$(ProjectDir)files\build_scripts\"
call "copy.bat"
For me, the reason was that the build created a platform folder on the build output folder (x86), and the fix was to change the solution platform from 'Mixed Platforms' to 'Any CPU' in VS
