• Create Account

### #ActualBinaryPhysics

Posted 07 January 2013 - 11:34 AM

Okay, I'm being to become slightly frustrated. What am I doing wrong?

I took the original advise that was given to me and simply added the batch to the end of sample-script. That work with the exception that any batch style commands presented in the batch file cause errors.

I decided to go back and write straight to the hook. Nothing happened at all.

More research and I discovered a concept called a 'shebang' which dictates the program that the script is meant to run in. So I now have:

#! C:\System32\cmd

CALL "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64
MSBuild Project.sln

Which does... Nothing at all. I can see that the console interpretor is opened because the copyright information appears every time I commit but nothing is generated from the solution file. Simply calling 'MSBuild Project.sln' myself correctly builds an executable with no errors.

There isn't a massive amount of information on the Internet about this. Have I missed something incredibly obvious?

### #3BinaryPhysics

Posted 07 January 2013 - 11:29 AM

Okay, I'm being to become slightly frustrated. What am I doing wrong?

I took the original advise that was given to me and simply added the batch to the end of sample-script. That work with the exception that any batch style commands presented in the batch file cause errors.

I decided to go back and write straight to the hook. Nothing happened at all.

More research and I discovered a concept called a 'shebang' which dictates the program that the script is meant to run in. So I now have:
#! C:\System32\cmdCALL "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64MSBuild Project.sln
Which does... Nothing at all. I can see that the console interpretor is opened because the copyright information appears every time I commit but nothing is generated from the solution file. Simply calling 'MSBuild Project.sln' myself correctly builds an executable with no errors.

There isn't a massive amount of information on the Internet about this. Have I missed something incredibly obvious?

### #2BinaryPhysics

Posted 07 January 2013 - 11:29 AM

Okay, I'm being to become slightly frustrated. What am I doing wrong?

I took the original advise that was given to me and simply added the batch to the end of sample-script. That work with the exception that any batch style commands presented in the batch file cause errors.

I decided to go back and write straight to the hook. Nothing happened at all.

More research and I discovered a concept called a 'shebang' which dictates the program that the script is meant to run in. So I now have:
#! C:\System32\cmdCALL "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64MSBuild Project.sln
Which does... Nothing at all. I can see that the console interpretor is opened because the copyright information appears every time I commit but nothing is generated from the solution file. Simply calling 'MSBuild Project.sln' myself correctly builds an executable with no errors.

There isn't a massive amount of information on the Internet about this. Have I missed something incredibly obvious?

### #1BinaryPhysics

Posted 07 January 2013 - 11:27 AM

Okay, I'm being to become slightly frustrated. What am I doing wrong?

I took the original advise that was given to me and simply added the batch to the end of sample-script. That work with the exception that any batch style commands presented in the batch file cause errors.

I decided to go back and write straight to the hook. Nothing happened at all.

More research and I discovered a concept called a 'shebang' which dictates the program that the script is meant to run in. So I now have:

#! C:\System32\cmd

CALL "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64
MSBuild Project.sln

Which does... Nothing at all. I can see that the console interpretor is opened because the copyright information appears every time I commit but nothing is generated from the solution file. Simply calling 'MSBuild Project.sln' myself correctly builds an executable with no errors.

There isn't a massive amount of information on the Internet about this. Have I missed something incredibly obvious?

PARTNERS