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: aspnetcore/migration/80-to-90.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Migrate from ASP.NET Core in .NET 8 to ASP.NET Core in .NET 9
3
3
author: wadepickett
4
4
description: Learn how to migrate an ASP.NET Core in .NET 8 to ASP.NET Core in .NET 9.
5
5
ms.author: wpickett
6
-
ms.date: 2/11/2024
6
+
ms.date: 05/06/2026
7
7
uid: migration/80-to-90
8
8
---
9
9
# Migrate from ASP.NET Core in .NET 8 to ASP.NET Core in .NET 9
@@ -78,7 +78,7 @@ Optimize the handling of static files in your web apps by replacing <xref:Micros
78
78
+ app.MapStaticAssets();
79
79
```
80
80
81
-
In MVC & Razor Pages apps you additionally need to chain a call to `.WithStaticAssets` after `MapRazorPages` or `MapControllerRoute` in `Program.cs`. For an example, see the <xref:fundamentals/static-files?view=aspnetcore-9.0&preserve-view=true>.
81
+
In MVC & Razor Pages apps, you additionally need to chain a call to `.WithStaticAssets` after `MapRazorPages` or `MapControllerRoute` in `Program.cs`. For an example, see the <xref:fundamentals/static-files?view=aspnetcore-9.0&preserve-view=true>.
82
82
83
83
ASP.NET Core automatically fingerprints and precompresses your static files at build and publish time, and then <xref:Microsoft.AspNetCore.Builder.StaticAssetsEndpointRouteBuilderExtensions.MapStaticAssets%2A> surfaces the optimized files as endpoints using endpoint routing with appropriate caching headers.
84
84
@@ -94,7 +94,7 @@ To resolve the fingerprinted file names from your app:
94
94
95
95
* In MVC & Razor Pages apps, the script and link tag helpers will automatically resolve the fingerprinted file names.
96
96
97
-
To resolve the fingerprinted file names when importing JavaScript modules, add a generated [import map](https://developer.mozilla.org/docs/Web/HTML/Element/script/type/importmap):
97
+
To resolve the fingerprinted file names when importing JavaScript modules, add a generated [import map](https://developer.mozilla.org/docs/Web/HTML/Reference/Elements/script/type/importmap):
98
98
99
99
* In Blazor apps, add the (<xref:Microsoft.AspNetCore.Components.ImportMap>) component to the `<head>` content of the app's root component, typically in the `App` component (`App.razor`):
100
100
@@ -103,7 +103,7 @@ To resolve the fingerprinted file names when importing JavaScript modules, add a
103
103
```
104
104
105
105
* In MVC & Razor pages apps, add `<script type="importmap"></script>` to the head of the main layout file, which is updated by the Import Map Tag Helper.
106
-
106
+
107
107
For more information, see the following resources:
@@ -21,7 +21,7 @@ NSwag offers the following capabilities:
21
21
* The ability to utilize the Swagger UI and Swagger generator.
22
22
* Flexible code generation capabilities.
23
23
24
-
With NSwag, you don't need an existing API—you can use third-party APIs that incorporate Swagger and generate a client implementation. NSwag allows you to expedite the development cycle and easily adapt to API changes.
24
+
With NSwag, you don't need an existing API—you can use partner APIs that incorporate Swagger and generate a client implementation. NSwag allows you to expedite the development cycle and easily adapt to API changes.
25
25
26
26
## Package installation
27
27
@@ -50,14 +50,14 @@ Use one of the following approaches to install the NSwag NuGet package:
50
50
* Right-click the project in **Solution Explorer** > **Manage NuGet Packages**
51
51
* Set the **Package source** to "nuget.org"
52
52
* Enter "NSwag.AspNetCore" in the search box
53
-
* Select the "NSwag.AspNetCore" package from the **Browse** tab and click **Install**
53
+
* Select the "NSwag.AspNetCore" package from the **Browse** tab and select **Install**
54
54
55
55
### [Visual Studio for Mac](#tab/visual-studio-mac)
56
56
57
57
* Right-click the *Packages* folder in **Solution Pad** > **Add Packages...**
58
58
* Set the **Add Packages** window's **Source** drop-down to "nuget.org"
59
59
* Enter "NSwag.AspNetCore" in the search box
60
-
* Select the "NSwag.AspNetCore" package from the results pane and click **Add Package**
60
+
* Select the "NSwag.AspNetCore" package from the results pane and select **Add Package**
61
61
62
62
### [Visual Studio Code](#tab/visual-studio-code)
63
63
@@ -105,14 +105,14 @@ You can take advantage of NSwag's code generation capabilities by choosing one o
105
105
106
106
### Generate code with NSwagStudio
107
107
108
-
* Install NSwagStudio by following the instructions at the [NSwagStudio GitHub repository](https://github.com/RicoSuter/NSwag/wiki/NSwagStudio). On the NSwag release page, you can download an xcopy version which can be started without installation and admin privileges.
108
+
* Install NSwagStudio by following the instructions at the [NSwagStudio GitHub repository](https://github.com/RicoSuter/NSwag/wiki/NSwagStudio). On the NSwag release page, you can download an xcopy version, which can be started without installation and admin privileges.
109
109
* Launch NSwagStudio and enter the `swagger.json` file URL in the **Swagger Specification URL** text box. For example, `http://localhost:5232/swagger/v1/swagger.json`.
110
-
*Click the **Create local Copy** button to generate a JSON representation of your Swagger specification.
110
+
*Select the **Create local Copy** button to generate a JSON representation of your Swagger specification.
111
111
112
112
:::image source="web-api-help-pages-using-swagger/_static/v6-nswag-NSwagStudio.png" alt-text="NSwag Studio imports the specification and exports a CSharp Client.":::
113
113
114
-
* In the **Outputs** area, click the **CSharp Client** checkbox. Depending on your project, you can also choose **TypeScript Client** or **CSharp Web API Controller**. If you select **CSharp Web API Controller**, a service specification rebuilds the service, serving as a reverse generation.
115
-
*Click**Generate Outputs** to produce a complete C# client implementation of the *TodoApi.NSwag* project. To see the generated client code, click the **CSharp Client** tab:
114
+
* In the **Outputs** area, select the **CSharp Client** checkbox. Depending on your project, you can also choose **TypeScript Client** or **CSharp Web API Controller**. If you select **CSharp Web API Controller**, a service specification rebuilds the service, serving as a reverse generation.
115
+
*Select**Generate Outputs** to produce a complete C# client implementation of the *TodoApi.NSwag* project. To see the generated client code, select the **CSharp Client** tab:
@@ -171,7 +171,7 @@ Manually add the highlighted lines to the `.csproj` file:
171
171
172
172
---
173
173
174
-
Enabling XML comments provides debug information for undocumented public types and members. Undocumented types and members are indicated by the warning message. For example, the following message indicates a violation of warning code 1591:
174
+
Enabling XML comments provides debug information for undocumented public types and members. The warning message indicates documented types and members. For example, the following message indicates a violation of warning code 1591:
175
175
176
176
```text
177
177
warning CS1591: Missing XML comment for publicly visible type or member 'TodoContext'
@@ -181,7 +181,7 @@ To suppress warnings project-wide, define a semicolon-delimited list of warning
To suppress warnings only for specific members, enclose the code in [#pragma warning](/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma-warning) preprocessor directives. This approach is useful for code that shouldn't be exposed via the API docs. In the following example, warning code CS1591 is ignored for the entire `TodoContext` class. Enforcement of the warning code is restored at the close of the class definition. Specify multiple warning codes with a comma-delimited list.
184
+
To suppress warnings only for specific members, enclose the code in [#pragma warning](/dotnet/csharp/language-reference/preprocessor-directives#pragma-warning) preprocessor directives. This approach is useful for code that shouldn't be exposed via the API docs. In the following example, warning code CS1591 is ignored for the entire `TodoContext` class. Enforcement of the warning code is restored at the close of the class definition. Specify multiple warning codes with a comma-delimited list.
0 commit comments