Update markdown files and release notes for Preview 7

Author: jamesmontemagno

.github/linters/.markdownlintignore

@@ -1,3 +1,4 @@
 # Ignore errors from before linting was enabled to allow incremental fixes
 
 **/api-diff/**
+**/prompts/**

.github/prompts/createprs-for-preview.prompt.md

@@ -1,18 +1,15 @@
----
-mode: agent
----
-
+# Create PRs for Preview
 
 Go through each folder in release-notes/10.0/preview7 and one at a time i want you do to the following:
 
-1. create a new branch names **dotnet10-p7-<name>** where <name> is the name of the file without the extension.
+1. create a new branch names **dotnet10-p7-{name}** where {name} is the name of the file without the extension.
 2. modify the file in some simple way by adding a new line at the end of the file with the text "Something about the feature" in it.
-3. commit the change with the message "Update <name> for preview 7" where <name> is the name of the file without the extension.
+3. commit the change with the message "Update {name} for preview 7" where {name} is the name of the file without the extension.
 4. push the branch to the remote repository.
-5. create a pull request with the title "Update <name> for preview 7" and the body "Please update the release notes here as needed for Preview 7.\n\n/cc @<reviewer>" where <name> is the name of the file without the extension and <reviewer> is assigned based on the assignment table below.
+5. create a pull request with the title "Update {name} for preview 7" and the body "Please update the release notes here as needed for Preview 7.\n\n/cc @{reviewer}" where {name} is the name of the file without the extension and {reviewer} is assigned based on the assignment table below.
 6. go back to the dotnet10-p7 branch and repeat the process for the next file.
 
-## Assignment Table (based on Preview 6 patterns):
+## Assignment Table (based on Preview 6 patterns)
 
 | File | Assignee(s) | Based on Preview 6 PR |
 |------|-------------|----------------------|
@@ -30,6 +27,7 @@ Go through each folder in release-notes/10.0/preview7 and one at a time i want y
 | wpf.md | @harshit7962 | #9948 |
 
 Here are the files you need to do this one at a time for:
+
 - aspnetcore.md
 - containers.md
 - csharp.md

.github/prompts/scaffoldpreview.prompt.md

@@ -1,6 +1,5 @@
----
-mode: agent
----
+# Scaffold Preview
+
 Create a new folder in the releasenotes/10.0/preview folder for preview7. Inside of it duplicate the folder structure and files that are in the preview6 folder and for each of the files use the following template based on the names of the product that the file is in. You can use the previous file as a reference for the content. Ignore the api-diff folder. Ignore the release.json file.
 
 Here is a sample of what aspnetcore.md should look like:
@@ -22,4 +21,4 @@ ASP.NET Core updates in .NET 10:
 
 Something about the feature
 
-``
+```

release-notes/10.0/preview/preview7/aspnetcore.md

@@ -34,7 +34,7 @@ app.UseExceptionHandler(new ExceptionHandlerOptions
 });
 ```
 
-For more information about this breaking change, see https://github.com/aspnet/Announcements/issues/524.
+For more information about this breaking change, see [this announcement](https://github.com/aspnet/Announcements/issues/524).
 
 ## Avoid cookie login redirects for known API endpoints
 
@@ -69,7 +69,7 @@ builder.Services.AddAuthentication()
     });
 ```
 
-For more information about this breaking change, see https://github.com/aspnet/Announcements/issues/525
+For more information about this breaking change, see [this announcement](https://github.com/aspnet/Announcements/issues/525).
 
 ## Passkey authentication improvements
 
@@ -124,6 +124,7 @@ To sign in with a passkey, use `SignInManager.PasskeySignInAsync()`:
 // 'credentialJson' is the JSON-serialized result from `navigator.credentials.get()`.
 var result = await signInManager.PasskeySignInAsync(credentialJson);
 ```
+
 ### Getting started with passkeys
 
 **For new applications:** The Blazor Web App project template now includes passkey functionality out of the box. Create a new Blazor app with passkey support using:
@@ -148,7 +149,7 @@ The [ASP.NET Core HTTPS development certificate](https://learn.microsoft.com/asp
 
 The project templates for *ASP.NET Core Empty* (`web`) and *Blazor Web App* (`blazor`) have been updated with a new option that when specified configures the created project to use the `.dev.localhost` domain name suffix, combining it with the project name to allow the app to be browsed to at an address like `https://myapp.dev.localhost:5036`:
 
-```
+```bash
 $ dotnet new web -n MyApp --localhost-tld
 The template "ASP.NET Core Empty" was created successfully.
 
@@ -268,7 +269,7 @@ The Blazor diagnostic metrics have been updated to follow OpenTelemetry naming c
 | `aspnetcore.components.render_diff` | Split into `aspnetcore.components.render_diff.duration` and `aspnetcore.components.render_diff.size` |
 | `aspnetcore.components.navigation` | `aspnetcore.components.navigate` |
 | `aspnetcore.components.event_handler` | `aspnetcore.components.handle_event.duration` |
-| `aspnetcore.components.update_parameters` | `aspnetcore.components.update_parameters.duration`
+| `aspnetcore.components.update_parameters` | `aspnetcore.components.update_parameters.duration` |
 
 ### Validate configured services for Blazor WebAssembly apps on build
 

release-notes/10.0/preview/preview7/libraries.md

@@ -5,12 +5,12 @@ Here's a summary of what's new in .NET Libraries in this preview release:
 - [Launch Windows processes in new process group](#launch-windows-processes-in-new-process-group)
 - [AES KeyWrap with Padding (IETF RFC 5649)](#aes-keywrap-with-padding-ietf-rfc-5649)
 - Post-Quantum Cryptography Updates
-    - [ML-DSA](#ml-dsa)
-    - [Composite ML-DSA](#composite-ml-dsa)
+  - [ML-DSA](#ml-dsa)
+  - [Composite ML-DSA](#composite-ml-dsa)
 - [PipeReader support for JSON serializer](#pipereader-support-for-json-serializer)
 - Networking
-    - [WebSocketStream](#websocketstream)
-    - [TLS 1.3 for macOS (client)](#tls-13-for-macos-client)
+  - [WebSocketStream](#websocketstream)
+  - [TLS 1.3 for macOS (client)](#tls-13-for-macos-client)
 
 .NET Libraries updates in .NET 10:
 
@@ -250,7 +250,8 @@ record Chunk(string Message, DateTime Timestamp);
 ```
 
 Note that all of this is serialized as JSON in the `Pipe` (formatted here for readability):
-```
+
+```json
 [
     {
         "Message": "The quick brown fox",
@@ -277,11 +278,11 @@ Traditional `WebSocket` APIs are low-level and require significant boilerplate:
 
 **WebSocketStream** addresses these pain points by providing a Stream-based abstraction over a WebSocket. This enables seamless integration with existing APIs for reading, writing, and parsing data, whether binary or text, and reduces the need for manual plumbing.
 
-**Common Usage Patterns**
+## Common Usage Patterns
 
 Here are a few examples of how `WebSocketStream` simplifies typical WebSocket workflows:
 
-**1. Streaming text protocol (e.g., STOMP)**
+### 1. Streaming text protocol (e.g., STOMP)
 
 ```csharp
 using Stream transportStream = WebSocketStream.Create(
@@ -295,7 +296,7 @@ var line = await transportReader.ReadLineAsync(cancellationToken); // Automatic
 transportStream.Dispose(); // Automatic closing handshake handling on `Dispose`
 ```
 
-**2. Streaming binary protocol (e.g., AMQP)**
+### 2. Streaming binary protocol (e.g., AMQP)
 
 ```csharp
 Stream transportStream = WebSocketStream.Create(
@@ -309,15 +310,15 @@ transportStream.Dispose();
 // `Dispose` automatically handles closing handshake
 ```
 
-**3. Reading a single message as a stream (e.g., JSON deserialization)**
+### 3. Reading a single message as a stream (e.g., JSON deserialization)
 
 ```csharp
 using Stream messageStream = WebSocketStream.CreateReadableMessageStream(connectedWebSocket, WebSocketMessageType.Text);
 // JsonSerializer.DeserializeAsync reads until the end of stream.
 var appMessage = await JsonSerializer.DeserializeAsync<AppMessage>(messageStream);
 ```
 
-**4. Writing a single message as a stream (e.g., binary serialization)**
+### 4. Writing a single message as a stream (e.g., binary serialization)
 
 ```csharp
 public async Task SendMessageAsync(AppMessage message, CancellationToken cancellationToken)

release-notes/10.0/preview/preview7/runtime.md

@@ -1,16 +1,7 @@
 # .NET Runtime in .NET 10 Preview 7 - Release Notes
 
-Here's a summary of what's new in the .NET Runtime in this preview release:
-
-- [Feature](#feature)
+This preview release does not contain new runtime features.
 
 .NET Runtime updates in .NET 10:
 
 - [What's new in .NET 10](https://learn.microsoft.com/dotnet/core/whats-new/dotnet-10/overview) documentation
-
-## Feature
-
-Something about the feature
-# Runtime updates in .NET 10 Preview 7 - Release Notes
-
-This preview release does not contain new runtime features.

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

@@ -8,7 +8,7 @@ Here's a summary of what's new in the .NET SDK in this preview release:
 
 - [What's new in .NET 10](https://learn.microsoft.com/dotnet/core/whats-new/dotnet-10/overview) documentation
 
-## Use the `any` RuntimeIdentifier with platform-specific .NET Tools <a id="any-rid-in-multi-rid-tools">
+## Use the `any` RuntimeIdentifier with platform-specific .NET Tools {#any-rid-in-multi-rid-tools}
 
 The [platform-specific .NET Tools](https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-10/sdk#platform-specific-net-tools) feature released in preview 6
 is great for making sure your tools are optimized for specific platforms that you target ahead-of-time. However, there are times where you won't know

release-notes/10.0/preview/preview7/winforms.md

@@ -1,10 +1,17 @@
-# Windows Forms in .NET 10 Preview 7 - Release Notes
+# WindowsWe've alsWe've also improved the rendering of special buttons within the PropertyGrid for dark mode. Previously, the ellipsis button used to open an editor and the drop-down button for ComboBox-type editors were not rendering well in dark mode. Now, these elements have dedicated renderers ensuring they appear consistently and at the same quality as the rest of the UI in dark mode.
+
+Everything mentioned above pertains specifically to dark mode improvements in Preview 7. Other functionalities remain unchanged in this release.ddressed the RichTextBox background issue in dark mode. Previously, a disabled RichTextBox would show a white background. Now it correctly displays the dark mode background. However, there's a known limitation: if the RichTextBox has formatted content, only the first few visible lines will appear correctly, and the formatting might not fully apply in the disabled state.
+
+As a temporary workaround, if maintaining full formatting in a disabled RichTextBox is essential, we recommend setting it to read-only and manually disabling selections. This helps achieve a better preview until a more permanent fix is available. Note that this limitation is due to the underlying RichTextBox control in the common controls library, and a full fix may require a future version update.
+
+## PropertyGrid Dark Mode Enhancementss in .NET 10 Preview 7 - Release Notes
 
 Here's a summary of what's new in Windows Forms in this preview release:
 
 ## ComboBox Dark Mode Rendering Fix
+
 In this update, we've resolved an issue where a disabled ComboBox displayed a white background instead of the appropriate dark mode color scheme. Now, regardless of whether the ComboBox is in editable, list, or simple mode, its constituent controls will correctly render with the proper dark mode background when disabled.
- 
+
 ## RichTextBox Dark Mode Improvement and Known Limitation
 We’ve also addressed the RichTextBox background issue in dark mode. Previously, a disabled RichTextBox would show a white background. Now it correctly displays the dark mode background. However, there's a known limitation: if the RichTextBox has formatted content, only the first few visible lines will appear correctly, and the formatting might not fully apply in the disabled state.