We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Visual Studio 2008 build msi command line?

pointeman
pointeman asked
on
Medium Priority
2,085 Views
Last Modified: 2013-11-26
This command line runs without error, but does not output any file. What am I doing wrong? However, It will build a usable .msi file within the IDE by clicking on the Setkup1 deployment project and choosing 'build'. I'm using Vista Businsess 64 & VS2008.

[BUILD VS2008 SOLUTION INSTALLER]
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" "E:\My Documents\Visual Studio 2008\Projects\myProjectName\Setup1\Setup1.vdproj" /build
Comment
Watch Question

Bob HoffmanDeveloper

Commented:
I believe you need to say what confuguration your building "/build Release".

Author

Commented:
I'll try it...

Author

Commented:
Well, it didn't error, but it also didn't write any output file.
Also tried /build "Release" , but still didn't write output file...
Here's the popup error when I make it error:

Use:
devenv  [solutionfile | projectfile | anyfile.ext]  [switches]
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:
/Build Builds the solution or project with the specified solution
 configuration. For example "Debug". If multiple platforms
 are possible, the configuration name must be enclosed in quotes
 and contain platform name. For example: "Debug|Win32".
/Clean Deletes build outputs.
/Command Starts the IDE and executes the command.
/Deploy Builds and then deploys the specified build configuration.
/Edit Opens the specified files in a running instance of this
 application. If there are no running instances, it will
 start a new instance with a simplified window layout.
/LCID Sets the default language in the IDE for the UI.
/Log Logs IDE activity to the specified file for troubleshooting.
/NoVSIP Disables the VSIP developer's license key for VSIP testing.
/Out Appends the build log to a specified file.
/Project Specifies the project to build, clean, or deploy.
 Must be used with /Build, /Rebuild, /Clean, or /Deploy.
/ProjectConfig Overrides the project configuration specified in the solution
 configuration. For example "Debug". If multiple platforms are
 possible, the configuration name must be enclosed in quotes
 and contain platform name. For example: "Debug|Win32".
 Must be used with /Project.
/Rebuild Cleans and then builds the solution or project with the
 specified configuration.
/ResetAddin Removes commands and command UI associated with the specified Add-in.
/ResetSettings Restores the IDE's default settings, optionally resets to
 the specified VSSettings file.
/ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.
/Run Compiles and runs the specified solution.
/RunExit Compiles and runs the specified solution then closes the IDE.
/SafeMode Launches the IDE in safe mode loading minimal windows.
/Upgrade Upgrades the project or the solution and all projects in it.
 A backup of these files will be created as appropriate.  Please
 see Help on 'Visual Studio Conversion Wizard' for more
 information on the backup process.
Product-specific switches:
/debugexe Open the specified executable to be debugged. The
 remainder of the command line is passed to this
 executable as its arguments.
/useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables
 instead of IDE paths for VC++ builds.
To attach the debugger from the command line, use:
 VsJITDebugger.exe -p <pid>
 
Bob HoffmanDeveloper

Commented:
I'm on Vs 2005. Don't you have a solution file? (.sln) If so that's what you create the project from. The output will do in the bin/release in you project root. Besure to delete what every is in bin/release prior to the build that way you know for sure it's been created.
try somthing like this:
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" "E:\My Documents\Visual Studio 2008\Projects\myProjectName\Setup1\Setup1.sln" /build Release
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.