Skip to content

Commit f25c209

Browse files
Fix file-based app headings in preview.6 release notes (#9975)
Fixes the heading level for the file-based apps notes
1 parent f023a1b commit f25c209

File tree

1 file changed

+2
-2
lines changed
  • release-notes/10.0/preview/preview6

1 file changed

+2
-2
lines changed

release-notes/10.0/preview/preview6/sdk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ var greeting = greeter.Greet(args.Length > 0 ? args[0] : "World");
149149
Console.WriteLine(greeting);
150150
```
151151
152-
## App file and directory path available at runtime
152+
### App file and directory path available at runtime
153153
154154
It's sometimes useful when authoring file-based apps to know at runtime the full path to the application source file and/or directory. This information is now available via the [`System.AppContext.GetData` method](https://learn.microsoft.com/dotnet/api/system.appcontext.getdata) when running file-based apps from source, e.g. `dotnet run app.cs`. The file path is available using the name `"EntryPointFilePath"`, and the directory via the name `"EntryPointFileDirectoryPath"`. Note that this data is not available after the application has been published or converted to a project-based app. Following is an example of using `AppContext` as well as the [`System.Runtime.CompilerServices.CallerFilePath` attribute](https://learn.microsoft.com/dotnet/api/system.runtime.compilerservices.callerfilepathattribute) to obtain the path to the C# source file:
155155
@@ -186,7 +186,7 @@ static class AppContextExtensions
186186
}
187187
```
188188
189-
## Enhanced shebang support
189+
### Enhanced shebang support
190190
191191
File-based apps support for shebang-based direct shell execution has been enhanced, again based on your feedback.
192192

0 commit comments

Comments
 (0)