Call batch in build event visual studio 2013

Question

0.00/5 (No votes)

See more:

I write batch file to copy folders from solution to another in visual studio 2013.

I wanna execute this file in build event by this code

CALL "..\CopyFilesToProducts.bat"

It gives me the below error

Error 41 The command "CALL "..\CopyFilesToProducts.bat"" exited with code 9009.

Posted 13-May-15 22:46pm

Osama Abu Sitta

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2015-05-13T23:02:00

Solution 1

The most likely reason is that it's not a fully qualified path - it's a relative path, and I've seen this before as an intermittent problem with VS builds. Changing to a full path:

CALL "C:\MyApps\CopyFilesToProducts.bat"

should cure it.

I suspect that the "current folder" that VS uses as the starting point for the relative path specification depends on the last operation it needed to do as part of teh actual build operation, but I'm not sure.

Posted 13-May-15 23:02pm

OriginalGriff

Comments

Richard Deeming 14-May-15 8:39am

Since the path seems to be relative to the solution, it would probably be a better idea to use the available path placeholders - for example, $(SolutionDir).

That way, the build won't break if you move the solution to a different path. :)

Osama Abu Sitta · Answer 2 · 2015-05-14T03:24:00

I am sorry because after I search and trace I found that,
I don't have problem with Visual Studio my problem was in cmd on local user environment variable ,

I found two solutions for this issue :
1 - Open Visual Studio as administrator

2 - changed local user environment variable path

right click on My Computer > Properties > Advanced System Setting > environment variable > Path [Edit value to C:\Windows\System32; ]