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
Added `needs-breaking-change-doc-created` label because this PR has the `breaking-change` label.
93
+
Added `needs-breaking-change-doc-created` label because this PR has the `breaking-change` label.
94
94
95
95
96
96
When you commit this breaking change:
@@ -103,5 +103,23 @@ configuration:
103
103
104
104
You can refer to the [.NET SDK breaking change guidelines](https://github.com/dotnet/sdk/blob/main/documentation/project-docs/breaking-change-guidelines.md)
105
105
description: Add breaking change instructions to PR.
106
-
onFailure:
107
-
onSuccess:
106
+
- description: Remind Telemetry PR authors of the telemetry guidelines
107
+
if:
108
+
- payloadType: Pull_Request
109
+
- labelAdded:
110
+
label: Area-Telemetry
111
+
then:
112
+
- addReply:
113
+
reply: >-
114
+
This PR has been labeled with `Area-Telemetry`. Please ensure that any telemetry changes in this PR
115
+
116
+
* comply with the [published guidance](https://learn.microsoft.com/dotnet/core/tools/telemetry#data-points)
117
+
* are added to the [repo-local telemetry documentation](./documentation/project-docs/telemetry.md)
118
+
* get a matching .NET Docs issue raised to document the telemetry changes
119
+
* Go to https://learn.microsoft.com/dotnet/core/tools/telemetry
120
+
* Scroll down to the bottom and click the 'Open a documentation issue' link to create an issue with pre-filled details
Copy file name to clipboardExpand all lines: documentation/general/dotnet-run-file.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,8 @@ Additionally, the implicit project file has the following customizations:
32
32
33
33
-`PublishAot` is set to `true`, see [`dotnet publish file.cs`](#other-commands) for more details.
34
34
35
+
-`UserSecretsId` is set to a hash of the entry point file path.
36
+
35
37
-[File-level directives](#directives-for-project-metadata) are applied.
36
38
37
39
- The following are virtual only, i.e., not preserved after [converting to a project](#grow-up):
@@ -287,16 +289,16 @@ The build is performed using MSBuild APIs on in-memory project files.
287
289
If an up-to-date check detects that inputs didn't change in subsequent `dotnet run file.cs` invocations,
288
290
building is skipped (as if `--no-build` option has been passed).
289
291
The up-to-date check is not 100% precise (e.g., files imported through an implicit build file are not considered).
290
-
It is possible to enforce a full build using `--no-cache` flag or `dotnet build file.cs`.
292
+
It is possible to enforce a full build using `--no-cache` flag or `dotnet build file.cs`
293
+
(for a more permanent opt-out, there is MSBuild property `FileBasedProgramCanSkipMSBuild=false`).
291
294
Environment variable [`DOTNET_CLI_CONTEXT_VERBOSE=true`][verbose-env] can be used to get more details about caching decisions made by `dotnet run file.cs`.
292
295
293
296
There are multiple optimization levels - skipping build altogether, running just the C# compiler, or running full MSBuild.
294
297
We always need to re-run MSBuild if implicit build files like `Directory.Build.props` change but
295
298
from `.cs` files, the only relevant MSBuild inputs are the `#:` directives,
296
299
hence we can first check the `.cs` file timestamps and for those that have changed, compare the sets of `#:` directives.
297
300
If only `.cs` files change, it is enough to invoke `csc.exe` (directly or via a build server)
298
-
re-using command-line arguments that the last MSBuild invocation passed to the compiler
299
-
(you can opt out of this via an MSBuild property `FileBasedProgramCanSkipMSBuild=false`).
301
+
re-using command-line arguments that the last MSBuild invocation passed to the compiler.
300
302
If no inputs change, it is enough to start the target executable without invoking the build at all.
0 commit comments