You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
var projectArg = new Arg("Project", "", "string", "The project or solution file to operate on. If not specified, the command searches the current directory for one. If more than one solution or project is found, an error is thrown.") { IsProject = true };
22
22
var solutionArg = new Arg("Solution", "", "string", "The solution file to use. If this argument is omitted, the command searches the current directory for one. If it finds no solution file or multiple solution files, the command fails.") { IsProject = true };
23
23
var propsArg = new Arg("Props", "--property", "IEnumerable<(string name, string value)>", "MSBuild options for setting properties.") { IsCollection = true };
@@ -229,15 +229,6 @@ using Internal;
229
229
paraStart,
230
230
"For executable projects targeting .NET Core 3.0 and later, library dependencies are copied to the output folder. This means that if there isn't any other publish-specific logic (such as Web projects have), the build output should be deployable.",
"new DotNetBuild().WithConfiguration(configuration)",
238
-
" .Build().EnsureSuccess();",
239
-
codeFinish,
240
-
exampleFinish,
241
232
CreateCliRef("dotnet-build")
242
233
],
243
234
["build", "$Project"],
@@ -1088,19 +1079,6 @@ using Internal;
1088
1079
paraStart,
1089
1080
"To run the application, the dotnet run command resolves the dependencies of the application that are outside of the shared runtime from the NuGet cache. Because it uses cached dependencies, it's not recommended to use dotnet run to run applications in production. Instead, create a deployment using the dotnet publish command and deploy the published output.",
1090
1081
paraFinish,
1091
-
exampleStart,
1092
-
codeStart,
1093
-
"new DotNetNew()",
1094
-
" .WithTemplateName(\"console\")",
1095
-
" .WithName(\"MyApp\")",
1096
-
" .WithForce(true)",
1097
-
" .Run().EnsureSuccess();",
1098
-
"",
1099
-
"",
1100
-
"new DotNetRun().WithWorkingDirectory(\"MyApp\")",
1101
-
" .Build().EnsureSuccess();",
1102
-
codeFinish,
1103
-
exampleFinish,
1104
1082
CreateCliRef("dotnet-run")
1105
1083
],
1106
1084
["run"],
@@ -1636,6 +1614,33 @@ using Internal;
1636
1614
/// <#= comment #>
1637
1615
<#
1638
1616
}
1617
+
1618
+
var exampleFile = Path.Combine("..", "CSharpInteractive.Tests", "UsageScenarios", "Comments", $"{command.Name}Scenario.txt");
1619
+
if (File.Exists(exampleFile))
1620
+
{
1621
+
var exampleLines = File.ReadAllLines(exampleFile);
1622
+
if (exampleLines.Length > 0)
1623
+
{
1624
+
#>
1625
+
/// <#= exampleStart #>
1626
+
///<#= codeStart #>
1627
+
<#
1628
+
var doc = new XmlDocument();
1629
+
foreach (var exampleLine in exampleLines.Select(i => i.TrimEnd()))
1630
+
{
1631
+
var node = doc.CreateElement("root");
1632
+
node.InnerText = exampleLine;
1633
+
var line = node.InnerXml;
1634
+
#>
1635
+
/// <#= line #>
1636
+
<#
1637
+
}
1638
+
#>
1639
+
///<#= codeFinish #>
1640
+
/// <#= exampleFinish #>
1641
+
<#
1642
+
}
1643
+
}
1639
1644
#>
1640
1645
/// </summary>
1641
1646
/// <param name="Args">Specifies the set of command line arguments to use when starting the tool.</param>
// Builds the library project, running a command like: "dotnet msbuild /t:Build -restore /p:configuration=Release -verbosity=detailed" from the directory "MyLib"
893
939
result=newMSBuild()
@@ -899,8 +945,8 @@ result = new MSBuild()
899
945
.Build().EnsureSuccess();
900
946
901
947
// The "result" variable provides details about a build
For more details how to use TeamCity service message API please see [this](https://github.com/JetBrains/TeamCity.ServiceMessages) page. Instead of creating a root message writer like in the following example:
0 commit comments