text: IntroductionI take this opportunity to write about the Command line switches for making our .NET Project Release Builds with out much fuss. The Reason am writing this is that this topic mentioned above is much ignored topic across .NET developers circles. ...
  De "D:\TestWinApp\testWinApp\testWinApp\ testWinApp.csproj".
  Suppose if you give a wrong path of a solution file then the following Error Message will be thrown.:
  Devenv SwitchesUse the following command line switches to display the integrated development environment and perform the described task.
  Use the following command line switches to perform the described task. These command line switches do not display the integrated development environment.
  devenv /build ConfigName [/project ProjName] [/projectconfig ConfigName] SolutionName
  ArgumentsConfigName Required. The solution configuration name. SolutionName Required. The path and name of the solution. If you want to build a single project configuration, use the /project ProjName argument to specify which project to build and optionally supply the /projectconfig configandplatformname argument.
  
  Run the the following command in Visual command Promptdevenv /build Debug "<Path-Of-the-Solution-File>"
  This Command will build the Solution in the Debug Mode
  Here is the output
  2) /out -Allows you to specify a file to receive errors when you build using the command line arguments
  devenv /out FileName
  ArgumentsFileName Required. The path and name of the file to receive errors when you build an executable.
  Remarks
  If a file name that does not exist is specified, the file is created automatically. If the file already exists, the contents are deleted before running the current build.
  Command line build errors are displayed in the Command Prompt window and the Solution Builder view of the Output window. This option is useful if you are running unattended builds and need to see the results.
  devenv /run /out "c:\MyErrorLog.txt" "D:\CUT1.3\POSClient\POSClient.sln"
  the output of the command from MyErrorLog.txt which got created under C:\ , Becoz of build problems of PosClient Solution
  ------ Build started: Project: POS, Configuration: Debug .NET ------
  Preparing resources...Updating references...The dependency 'POSUI' could not be found.The dependency 'Utility' could not be found.The dependency 'ControllerInterface' could not be found.The dependency 'HECUIControls' could not be found.The dependency 'CommonDataEntity' could not be found.Cannot copy assembly 'ProcessController' to file 'D:\CUT1.3\deploymentarea\apps\posclient\ProcessController.dll'. The process cannot access the file because it is being used by another process.Performing main compilation...D:\CUT1.3\POSClient\POS\ProcessController\Generic\ApplicationController.cs(17,46): error CS0234: The type or namespace name 'Partner' does not exist in the class or namespace 'HEC.POS.Presentation.ProcessController' (are you missing an assembly reference?)
  Build complete -- 1 errors, 0 warningsBuilding satellite assemblies...
  ---------------------- Done ----------------------
  Build: 22 succeeded, 6 failed, 0 skipped
  3) Lot of other Command line Switches like Release , Re-Build according to the Requirement and need
  Important Tips
  1) You can make all these commands as a Batch Process (Batch File) and you can deploy your Release Builds with out much fuss and in much lesser time. It will save a lot of time for Configuration Managers and Developers.
  2) Build Process for .Net Developers they can easily build there project with out opening the solutions with Windows Script using Shell Commands. if there are any bugs while building it will create file called status.txt and states bugs in that. The Next Article I will be writing more about it
  3) Another Important point I want to make is that if we Consolidate all these command into a Single Batch file , then it will be very much helpful for us in making our Release Builds.
  Advantages
  1) We hope to make many aspects of? Devenv /build? a little easier to use, but hopefully this information will make this feature less mystifying for the next time you want to use it.
  2) If you look at the time it takes for loading the VS.Net projects and building. Using these Command line switches is comparably lot less then manual loading (Start->Programs->Visual Studio for .NET) of VS.Net project solutions and building. On the whole it will make the process of Building the Solutions much faster.
  Build a .NET Solution or Project from the Command Line
  Thread Synchronization using VS.NET 2005
  Hi,Is there any way to Add a project into solution from command line.Thanks.
  Hi there,Is it possible to add projects (.csproj/.vdproj) to solution (.sln) via command line, kindly let me know, thanks.. to use command line interfaceAbility to target all .Net framework version i.e. 1.1, 2.0, 3.0 and 3.5Supports XML based configurationSupports both project and file referencesAutomatically generates the “complete ordered build list” for a given project – No touch maintenance.Ability to detect and display circular dependenciesPerform parallel build - automatically decides which of the projects in the generated build list can be built independently.Ability to handle proxy assembliesProvides visual clue to the build process e.g. showing “% completed”, “current status” etc.Generates detailed execution log both in XML and text formatEasily integrated with Cruise-Control.Net continuous integration systemCan use custom logger like XMLLogger when targeting 2.0 + versionAbility to parse error logsAbility to deploy built assemblies to user specified locationAbility to synchronize source code with source-control systemVersion management capability.