I am trying to build a vdproj file using devenv. I have read several post that explain how I can do it by embedding a <exec/> task in the project file and having it invoke devenv. I'm trying to build the project outside of visual studio using a CI tool. My concern with adding this code into the project file is how somebody is effected building it within visual studio.
I have read that I can call the command as follows:
devenv "c:\your solution file.sln"/Project"c:\your setup project file.vdproj"/Build"Release"when I run it using: devenv my.sln /project myproject/myproject.vdproj /Build "Release"
I get a usage error print out that says:
The first argument for devenv is usually a solution file or project file. You can also use any other file as the first argument if you want to have the file open automatically in an editor. When you enter a project file, the IDE looks for an .sln file with the same base name as the project file in the parent directory for the project file. If no such .sln file exists, then the IDE looks for a single .sln file that references the project. If no such single .sln file exists, then the IDE creates an unsaved solution with a default .sln file name that has the same base name as the project file. Command line builds: devenv solutionfile.sln /build [ solutionconfig ] [ /project projectnameorfile [ /projectconfig name ] ] Available command line switches:
What is the correct way to be able to call a vdproj file from a command line so I can build it via the command line from within a CI tool?