Project Options (Build)
|Conditional Compilation Symbols||Global defines that will be made available for checking by $IFDEF/$IFNDEF statements inside the project code.||DEBUG;TRACE on the Debug profile; empty for Release.|
|Framework Folder|| The folder where system (framework) assemblies are located.
Usually, framework assemblies will be referenced by a path such as "$(Framework)\mscorlib.dll" and this setting specifies the folder to substitute.
If empty, the folder of the framework currently running the compiler will be used (i.e. 2.0 when running under Visual Studio 2005, 3.5 under 2008, etc).
|Enable Asserts|| Normally, you set this off for Release and on for Debug configurations, as you probably do not want your users to see assertion warnings.
Note: This setting also affects Class Contracts.
True for the Debug profile; false for Release.
|Warn On Case Mismatch||Warns if an identifier does not match the case of the item called.||False|
|Enable Code Flow Analysis||Toggles warnings for uninitialized variables and unreachable code.||True|
|Run Code Analysis||Invokes FXCop (if present) to do static code analysis.||False|
|Require Explicit Initialization Of Local Variables||By default, all local variables are initialized with 0 for numeric types and nil for reference types and strings. If this option is turned on, warnings will be generated during the build process if the value of the uninitialized variable is used.||False|
|Optimize Code||Set this option to generate optimized code. It will create code that is not quite as debuggable as non-optimized code, it can, for example, appear to jump to the wrong line, but it will always execute the right line.||False for Debug; True for Release.|
|"Future" Helper Class Name||Name of the custom helper class that will be used to implement the future feature. By default, the predefined FutureHelper class is used. See the future feature for more details about this feature and custom helper classes.||Empty, FutureHelper will be used.|
|CPU Type|| The CPU type indicates what CPU the code will run on.
Anything but Any CPU will only run under that specific platform (even though the code might be capable of running anywhere). For example, an application flagged as x64 will refuse to run anywhere but on an x64 system and an application marked as x86 will always run as 32bit (on x64 systems, it will run in 32bit compatibility mode).
Any CPU will run as native code on any system (i.e. 64bit on a 64bitter).
|Treat Warnings as Errors|| An error always stops a compilation, whereas warnings do not.
Set this option to true if you do not want compiles to proceed either.
|Suppress warnings||List of warnings or hints to suppress. This option is useful if certain warnings are not relevant for your code.||Empty|
|Output Path||The folder where the generated assembly, debug symbol files and XML comment files will be written.||Bin\ProfileName (Bin\Debug or Bin\Release by default).|
|Register for COM Interop||Registers types marked with the ComVisible attribute for consumption via COM. This is the same as running regasm.exe on the final .dll. Links to ComVisible in the .NET documentation.||False|
|Generate XML documentation||Toggles whether XML documentation files will be generated from XmlDoc comments inside the code. XML documentation files can be used by the IDE to show information and help in Method Hints when consuming the generated assembly.||False|
|XML Documentation Warning Level||Specifies the kinds of missing XML Documentation tags for which warnings should be generated (only applies if XML Documentation is enabled).||Public|
|Generate XML for undocumented members||Toggles whether XML is generated for undocumented members.||False|
|Generate PDB Debug Info||Set this option to true, if you want Microsoft PDB debug symbols to be generated (only available if the compiler is running under .NET). See the Output Path option above.||True for Debug; False for Release.|
|Generate MDB Debug Info||Set this to true, if you want Mono MDB debug symbols to be generated (only available if the compiler is running under Mono). See the Output Path option above.||True for Debug; False for Release.|
- Project Options
- IDE Integration
- Cross Linking
- Enforce Case
- Code Flow Analysis
- FxCop Code Analysis