Question

Ok, here’s the breakdown of my project: I have a web project with a ‘Scripts’ subfolder. That folder contains a few javascript files and a copy of JSMin.exe along with a batch file that runs the JSMin.exe on a few of the files. I tried to set up a post build step of ‘call ‘$(ProjectDir)Scripts\jsmin.bat”. When I perform the build, the batch file is always ‘exited with code 1.’ This happens going through Visual Studio or through the msbuild command line. I can run the batch file manually from the Scripts folder and it seems to work as expected, so I’m not sure what the issue here is. The $(ProjectDir)Scripts\jsmin.bat call is in quotes because $(ProjectDir) could have spaces (and in fact does on my machine). I’m not sure what to do at this point. I’ve tried removing the contents of the batch file as the post build step but that doesn’t seem to work either.

Ideally I would like to solve this problem through the post or pre-build steps so that the build manager won’t have to go through an extra step when deploying code.

Thanks!

Answer 1

If you have something in your custom build step that returns an error code, you can add:

exit 0 

as the last line of your build step. This will stop the build from failing.