This tab of the Make VS.NET / Delphi Prism action configures information about the project or solution to be built or the project, solution, or assembly info file to be updated.

 

Filename: The Visual Studio project or solution file to build or the assembly attribute or resource file to update.  The following file extensions are supported: .sln, .csproj, .vbproj, .vcproj, .vjsproj, .csdproj, .vbdproj, .vdproj, .oxygene, .wixproj, .rc*, .cs, .vb, .jsl, .cpp.

 

Notes:

 

Don't build: Does not build the projects; only updates versions, base address, or other properties that are specified.

 

Build behavior: Specifies which build type to perform:

 

Note: VS.NET 2002/2003 contain a bug that prevents clean from doing anything for non-C++ projects, and VS.NET 2002/2003 always rebuilds non-C++ projects even when Build is specified.

 

Clear the target executable's read-only flag: Clears the read-only flag for the output file (target executable) of each matching configuration of each project if set.

 

Post-process successfully built projects on solution build failure: If checked, when building a multi-project solution, if some projects build successfully but one or more projects fail to build, any version increment logic (configured on the Versions tab) will be performed for the successfully built projects.  If unchecked, the step will not perform post-processing if any projects in the solution fail to build.  This option is most useful with VC++ solutions to ensure that versions get incremented in all cases.

 

Parse build output for failed projects:  Sometimes, devenv.com will return a success (0) exit code even if one or more projects failed to build.  If this box is checked, the action also parses the build output to verify that 0 projects failed to build, and if an error condition is found, the step will also be marked as failed.  This flag does not apply when building Visual Studio 2005 and later and Delphi Prism projects with msbuild.exe.

 

Configuration: Specifies the project or solution configuration to build.  Choose All to build all configurations, enter a valid configuration name or select one from the list, or enter a regular expression to match one or more configurations (i.e., Debug.* to match all configurations beginning with Debug).  When building a .sln file, you must provide a valid solution configuration; when building individual project files, enter a valid project configuration (the Configuration drop-down list is populated from the Filename provided when possible).

 

Visual Studio .NET adds the concept of solution configurations in addition to project configurations.  Solution configurations are accessed from the properties of the solution (by right-clicking on a solution in the Solution Explorer, choosing Properties, and clicking on the Configuration Properties tree item), not the project itself.  For each solution configuration, VS.NET allows you to specify which project configuration will be built and also allows you to include or exclude projects from a build (accessed from Build | Configuration Manager on the menu in Visual Studio .NET).  These same settings will be used by Visual Build when building the solution.

 

Update the output directory for each project: If provided, the output directory for each matching configuration of each project will be updated to the specified value.

 

Notes:

 

Restore read-only attribute of any files modified by action: If checked, any project files modified for the build (to set/increment versions, properties, etc.) which are marked read-only before modification will be set back to read-only after being modified.

 

Include devenv /project flag when building individual projects: If checked, an individual project file is specified in the Filename field, and devenv is used to build (on the Options tab), the /project flag will be included to specify that only that project should be built even if devenv finds a solution containing that project.  This can be needed to prevent devenv from finding and building a related solution instead, but in other circumstances it can cause a build error.