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
/// Entry point for the build task. To use the build task in a csproj, the <c>UsingTask</c> element must be specified before defining the task. The task will
106
+
/// have the same name as the class, followed by the parameters. In this case, it would be <see cref="RubberduckPreBuildTask"/> element. See <c>Rubberduck.Deployment.csproj</c>
107
+
/// for usage example. The public properties are used as a parameter in the MSBuild task and are both settable and gettable. Thus, we must read from the properties when
108
+
/// we run the <c>Execute</c> which influences the behvaior of the task.
/// Full path to the directory containing the templates we need to modify.
12
+
/// </summary>
10
13
[Required]
11
14
publicstringWorkingDir{get;set;}
12
15
16
+
/// <summary>
17
+
/// Full path to the directory where we want to place our modified files.
18
+
/// </summary>
13
19
[Required]
14
20
publicstringOutputDir{get;set;}
15
21
22
+
/// <remarks>
23
+
/// Entry point for the build task. To use the build task in a csproj, the <c>UsingTask</c> element must be specified before defining the task. The task will
24
+
/// have the same name as the class, followed by the parameters. In this case, it would be <see cref="RubberduckPreBuildTask"/> element. See <c>Rubberduck.Deployment.csproj</c>
25
+
/// for usage example. The public properties are used as a parameter in the MSBuild task and are both settable and gettable. Thus, we must read from the properties when
26
+
/// we run the <c>Execute</c> which influences the behvaior of the task.
0 commit comments