Error 7 The Command Exited With Code 9009
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn the command xcopy exited with code 9009 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users
Error Msb6006 Cmd Exe Exited With Code 9009
Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping error msb3073 exited with code 9009 each other. Join them; it only takes a minute: Sign up nuget install exit code 9009 up vote 6 down vote favorite When build my solution, I got an error: Error 116 The command "nuget install “C:\Mycode\Test\some\ClassLibs\WCF\ServiceHosts\Monitor\packages.config” -o exited with code 9009 post build event “C:\Mycode\Test\Some\ClassLibs\WCF\ServiceHosts\Monitor\packages.config”" exited with code 9009 I use VS 2012, Thanks. .net visual-studio build nuget share|improve this question edited Feb 26 '13 at 19:45 asked Feb 26 '13 at 19:25 user1108948 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote accepted Error 9009 means that Visual Studio cannot find an executable - typically one used in a pre or post build step. In this instance, it seems that NuGet is the source
Exited With Code 9009 Visual Studio 2012
of the problem. Is it possible that you are using a solution that manages dependencies using NuGet (and probably has the "Enable NuGet package restore" option enabled), but you haven't yet loaded the NuGet extension into Visual Studio 2012? To confirm if this is the case, go to the Tools menu, and click "Extensions and Updates", select installed and type nuget Return into the search box at the top right corner of the Extensions and Updates form. If it's installed, you should see it listed with a version number - for example 2.4.40116.9051 which I believe is the most recent release as I type this. If you don't find it, select "online" from the list on the left hand side of the Extensions and Updates form. Locate the NuGet Package Manager entry (quite possibly the first item on the list) and click "download" to grab it. share|improve this answer answered Feb 26 '13 at 19:55 Richard J Foster 1,8301328 1 I do have NuGet in Visual Studio 2012. I thought that I should modify the project file but not sure. –user1108948 Feb 26 '13 at 20:10 Possibly. The error doesn't look quite kosher because I believe the parameter after the -o should be a directory, and it appears to be a file. Do you get more/better information if you execute the install command directly f
here for a quick overview of exited with code 9009 visual studio 2013 the site Help Center Detailed answers to any questions gacutil exited with code 9009 you might have Meta Discuss the workings and policies of this site About
Error Msb3073 The Command Exited With Code 9009
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions http://stackoverflow.com/questions/15097538/nuget-install-exit-code-9009 Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MSB3073 'command' exited with code 9009 up http://stackoverflow.com/questions/22730003/msb3073-command-exited-with-code-9009 vote 4 down vote favorite 3 Whenever I execute this command it throws error MSB3073 with code 9009 $(WixPath)heat dir $(Publish) -dr INSTALLFOLDER -ke -srd -cg DatoCheckerWebComponents -var var.publishDir -gg -out $(WebSiteContentCode) The entire build file is here: for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways https://www.experts-exchange.com/questions/21956311/What-does-this-mean-exited-with-code-9009.html to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > What does this mean (exited with code 9009) Want to Advertise Here? Solved What does this mean (exited with code 9009) Posted on 2006-08-16 Visual C++.NET 2 Verified Solutions 3 Comments 31,396 Views Last Modified: 2012-05-05 Hi All, Error 1 The command exited with "C:\Documents and Settings\sudhakar\Desktop\Prithvi\Prithvi\HAT.DriveThruDetector\\..\..\..\..\PostBuild.bat C:\Documents and Settings\sudhakar\Desktop\Prithvi\Prithvi\HAT.DriveThruDetector\\..\..\..\..\ C:\Documents and Settings\sudhakar\Desktop\Prithvi\Prithvi\HAT.DriveThruDetector\bin\Release\ HAT.DriveThruDetector" exited with code 9009. HAT.DriveThruDetector I do not understand what does the above error code mean. Because of this I am not able to compile my files. Please help me in resoloving the issue. Thanks Sudhakar 0 Question by:sudhakar_koundinya Facebook Twitter LinkedIn Google LVL 15 Best Solution bylakshman_ce Error code 9009 means your .bat file was not found. I exited with code think the post build command is launched using the output directory as working directory, so if your .bat file is located in the project directory, Go to Solution 3 Comments LVL 15 Overall: Level 15 Visual C++.NET 11 Message Accepted Solution by:lakshman_ce2006-08-16 Error code 9009 means your .bat file was not found. I think the post build command is launched using the output directory as working directory, so if your .bat file is located in the project directory, you have to use the relative path from the output directory back to the project directory. Also take a look at this link http://www.kbalertz.com/908268/receive.build.error.message.Assembly.Registration.Visual.aspx 0 LVL 5 Overall: Level 5 Message Assisted Solution by:thegilb2006-08-16 a) Does your program compile and run ok in debug build? If not then the error is a bug in your code and you should debug it with your debugger (Press F5 to run your program with the debugger) b) Have you been writing build event scripts? If so it looks like your paths may not be correct. Try looking at the Build log (BuildLog.htm in your debug / release directory), and also check for any .InstallLog or .InstallState files and check them to see if they have any meaningful information in