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
Copy file name to clipboardExpand all lines: documentation/general/decouple-vs-and-net-sdk.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,7 +145,7 @@ Based on the value of the `RoslynCompilerType` property, the SDK (or compiler to
145
145
146
146
These values are recognized for property `RoslynCompilerType`:
147
147
-`Core`: use the compiler that comes with the .NET SDK
148
-
-`Framework`: use the compiler that comes with .NET Framework MSBuild
148
+
-`Framework`: use the compiler that comes with .NET Framework MSBuild (this option is [deprecated and will be removed in .NET 11](https://aka.ms/roslyn-compiler-type-framework))
149
149
-`FrameworkPackage`: download the Microsoft.Net.Sdk.Compilers.Toolset package which contains the .NET Framework compiler corresponding to the .NET SDK version
150
150
-`Custom`: the SDK will not override `RoslynTasksAssembly` and the other properties listed above - used for example by Microsoft.Net.Compilers.Toolset package which injects its own version of the build task
Copy file name to clipboardExpand all lines: documentation/general/dotnet-run-file.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -248,6 +248,16 @@ The directives are processed as follows:
248
248
(because `ProjectReference` items don't support directory paths).
249
249
An error is reported if zero or more than one projects are found in the directory, just like `dotnet reference add` would do.
250
250
251
+
Directive values support MSBuild variables (like `$(..)`) normally as they are translated literally and left to MSBuild engine to process.
252
+
However, in `#:project` directives, variables might not be preserved during [grow up](#grow-up),
253
+
because there is additional processing of those directives that makes it technically challenging to preserve variables in all cases
254
+
(project directive values need to be resolved to be relative to the target directory
255
+
and also to point to a project file rather than a directory).
256
+
Note that it is not expected that variables inside the path change their meaning during the conversion,
257
+
so for example `#:project ../$(LibName)` is translated to `<ProjectReference Include="../../$(LibName)/Lib.csproj" />` (i.e., the variable is preserved).
258
+
However, variables at the start can change, so for example `#:project $(ProjectDir)../Lib` is translated to `<ProjectReference Include="../../Lib/Lib.csproj" />` (i.e., the variable is expanded).
259
+
In other directives, all variables are preserved during conversion.
260
+
251
261
Because these directives are limited by the C# language to only appear before the first "C# token" and any `#if`,
252
262
dotnet CLI can look for them via a regex or Roslyn lexer without any knowledge of defined conditional symbols
253
263
and can do that efficiently by stopping the search when it sees the first "C# token".
Sets the \f[V]RuntimeIdentifier\f[R] to a platform portable \f[V]RuntimeIdentifier\f[R] based on the one of your machine.
332
-
This happens implicitly with properties that require a \f[V]RuntimeIdentifier\f[R], such as \f[V]SelfContained\f[R], \f[V]PublishAot\f[R], \f[V]PublishSelfContained\f[R], \f[V]PublishSingleFile\f[R], and \f[V]PublishReadyToRun\f[R].
333
-
If the property is set to false, that implicit resolution will no longer occur.
315
+
Sets the verbosity level of the command.
316
+
Allowed values are \f[V]q[uiet]\f[R], \f[V]m[inimal]\f[R], \f[V]n[ormal]\f[R], \f[V]d[etailed]\f[R], and \f[V]diag[nostic]\f[R].
317
+
For more information, see <xref:Microsoft.Build.Framework.LoggerVerbosity>.
0 commit comments