Recently considering joining the Daily Build function in a project management tool, study the command line compilation mode of the vs.net2003. I used to write a DAILY building tool specifically for VB6.0, why didn't I do a common? First, general mode is often more complicated, not well written. Second, there is a lot of articles about the compilation of the command line at that time. They have to teach me to manually write a module. If there is a reference to an Assembly or any resource file, you have to manually link ... but it is okay. I finally studied a little small results, so quickly and everyone, I hope to help some friends! Basic Technical Introduction: The command line is compiled, and the DEVENV.EXE file is mainly used in the "Microsoft Visual Studio .Net 2003 / Common7 / IDE /" directory. Usage: devenv [SolutionFile | Projectfile | Anyfile.ext] [Switches]
You can call DEVENV, specify solution files or project files with the first parameter. You can also call DEVENV to make the first parameter as any other type of file to be opened in the editor. If the project file is provided, the IDE will find the project file in the context of the solution with the project file in the same directory as the project file, open the project file in the context of the solution. If there is .sln file, the IDE will look up a single .sln file that references the item. If there is no such a single .sln file, the IDE will create an unsaveful solution with the default .sln file name, and the default file name has the same base name as the project file.
Command line generation: devenv solutionfile.sln / build solutionconfig [/ project Projectnameorfile [/ Projectconfig name]]]]]
Available command line switch:
/ Build Generates Specified Solution Configuration / Project Specifies Generating Projects Instead of Solution To specify / build to use / project / projectconfig Specify that the project configuration to be generated must specify / project to use / projectConfig / OUT to write the specified result Document / Rebuild and / Build Similar, but first enforce the mandatory cleaning / Clean cleaning generation result / deploy generates the specified solution configuration and then deploy it / run run the specified solution Configuration / Runexit Run the specified solution configuration and then terminate / command startup After executing the specified internal command line / mditabs Using tab Document interface / MDI Using MDI interface / FN Using the specified font name / fs Using the specified font size / LCID Using the specified language ID / NOVSIP Disable VSIP for VSIP test Developer License Key / SafeMode For stability, only the default environment and service / ResetskipPKGS allows the VSPackages that have been marked as load failed to load / migrateSettings to migrate some users in another version to set product-specific switches:
/ debugexe Opens the specified executable to be debugged. The rest of the command line is passed to this execution file as its parameters. / UseNV uses Path, include, libpath, and lib environment variables instead of using the IDE path generated by VC .
To attach a debugger from the command line, use: vs7jit.exe -p
November 28, November 28, Zhang Yuxiang