Compiles C# source into executables or modules. csc.exe on Windows or mcs on any other platform must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> All parameters are optional: <csc/> should suffice to produce a debug build of all *.cs files. However, naming an <tt>destFile</tt>stops the csc compiler from choosing an output name from random, and allows the dependency checker to determine if the file is out of date. <p> The task is a directory based task, so attributes like <b>includes="*.cs" </b> and <b>excludes="broken.cs"</b> can be used to control the files pulled in. By default, all *.cs files from the project folder down are included in the command. When this happens the output file -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destFile</tt> seems prudent. <p> <p> For more complex source trees, nested <tt>src</tt> elemements can be supplied. When such an element is present, the implicit fileset is ignored. This makes sense, when you think about it :) <p> References to external files can be made through the references attribute, or (since Ant1.6), via nested <reference> filesets. With the latter, the timestamps of the references are also used in the dependency checking algorithm. <p> Example <pre><csc optimize="true" debug="false" docFile="documentation.xml" warnLevel="4" unsafe="false" targetType="exe" incremental="false" mainClass = "MainApp" destFile="NetApp.exe" > <src dir="src" includes="*.cs" /> <reference file="${testCSC.dll}" /> <define name="RELEASE" /> <define name="DEBUG" if="debug.property"/> <define name="def3" unless="def3.property"/> </csc> </pre>
Compiles C# source into executables or modules. csc.exe on Windows or mcs on any other platform must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> All parameters are optional: <csc/> should suffice to produce a debug build of all *.cs files. However, naming an <tt>destFile</tt>stops the csc compiler from choosing an output name from random, and allows the dependency checker to determine if the file is out of date. <p> The task is a directory based task, so attributes like <b>includes="*.cs" </b> and <b>excludes="broken.cs"</b> can be used to control the files pulled in. By default, all *.cs files from the project folder down are included in the command. When this happens the output file -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destFile</tt> seems prudent. <p> <p> For more complex source trees, nested <tt>src</tt> elements can be supplied. When such an element is present, the implicit fileset is ignored. This makes sense, when you think about it :) <p> References to external files can be made through the references attribute, or (since Ant1.6), via nested <reference> filesets. With the latter, the timestamps of the references are also used in the dependency checking algorithm. <p> Example <pre><csc optimize="true" debug="false" docFile="documentation.xml" warnLevel="4" unsafe="false" targetType="exe" incremental="false" mainClass = "MainApp" destFile="NetApp.exe" > <src dir="src" includes="*.cs" /> <reference file="${testCSC.dll}" /> <define name="RELEASE" /> <define name="DEBUG" if="debug.property"/> <define name="def3" unless="def3.property"/> </csc> </pre>
@@ -49,7 +49,7 @@ See details in the documentation of the <a href="../CoreTypes/regexp.html#implem
<td valign="top">flags</td>
<td valign="top">flags</td>
<td valign="top">The flags to use when matching the regular expression. For more
<td valign="top">The flags to use when matching the regular expression. For more
information, consult the Perl5 syntax<br />
information, consult the Perl5 syntax<br />
g : Global replacement. Replace all occurences found<br />
g : Global replacement. Replace all occurrences found<br />
i : Case Insensitive. Do not consider case in the match<br />
i : Case Insensitive. Do not consider case in the match<br />
m : Multiline. Treat the string as multiple lines of input, using "^" and "$" as the start or end of any line, respectively, rather than start or end of string.<br />
m : Multiline. Treat the string as multiple lines of input, using "^" and "$" as the start or end of any line, respectively, rather than start or end of string.<br />
s : Singleline. Treat the string as a single line of input, using "." to match any character, including a newline, which normally, it would not match.<br />
s : Singleline. Treat the string as a single line of input, using "." to match any character, including a newline, which normally, it would not match.<br />
@@ -60,7 +60,7 @@ See details in the documentation of the <a href="../CoreTypes/regexp.html#implem
<td valign="top">byline</td>
<td valign="top">byline</td>
<td valign="top">Process the file(s) one line at a time, executing the replacement
<td valign="top">Process the file(s) one line at a time, executing the replacement
on one line at a time (<i>true/false</i>). This is useful if you
on one line at a time (<i>true/false</i>). This is useful if you
want to only replace the first occurence of a regular expression on
want to only replace the first occurrence of a regular expression on
each line, which is not easy to do when processing the file as a whole.
each line, which is not easy to do when processing the file as a whole.
@@ -552,7 +552,7 @@ and the third from a tree rooted at C:\dev\buildtest\co\src\java all to a tree r
<h3>Description</h3>
<h3>Description</h3>
Creates a view label in StarTeam at the specified view. The label will be classified by StarTeam as a "build label". This task will fail if there already exexists in <i>viewname</i> a label with the same name as the <i>label</i> parameter.
Creates a view label in StarTeam at the specified view. The label will be classified by StarTeam as a "build label". This task will fail if there already exists in <i>viewname</i> a label with the same name as the <i>label</i> parameter.
<h3>Parameters</h3>
<h3>Parameters</h3>
See also <A href="#common-params">the required common StarTeam parameters</A>.<br></br>
See also <A href="#common-params">the required common StarTeam parameters</A>.<br></br>
@@ -686,7 +686,7 @@ See also <A href="#common-params">the required common StarTeam parameters</A>.<b
</tr>
</tr>
<tr>
<tr>
<td valign="top">asofdate</td>
<td valign="top">asofdate</td>
<td valign="top">List files, dates, and statusess as of this date.
<td valign="top">List files, dates, and statuses as of this date.
The date must be formatted in ISO8601 datetime
The date must be formatted in ISO8601 datetime
(<code>yyyy-MM-dd'T'HH:mm:ss</code>), ISO8601
(<code>yyyy-MM-dd'T'HH:mm:ss</code>), ISO8601
date(<code>yyyy-MM-dd</code>) or a user-defined SimpleDateFormat
date(<code>yyyy-MM-dd</code>) or a user-defined SimpleDateFormat
Thank you for your continuous support to the Openl Qizhi Community AI Collaboration Platform. In order to protect your usage rights and ensure network security, we updated the Openl Qizhi Community AI Collaboration Platform Usage Agreement in January 2024. The updated agreement specifies that users are prohibited from using intranet penetration tools. After you click "Agree and continue", you can continue to use our services. Thank you for your cooperation and understanding.
Stefan Bodewig