dotnet · gewarren · Jul 22, 2025 · Jul 22, 2025
@@ -16,13 +16,9 @@ Applying cost/benefit analysis, there's a good chance some wouldn't support the
 What type of application might be a candidate for cloud native?
 
 - Strategic enterprise systems that need to constantly evolve business capabilities/features
-
 - An application that requires a high release velocity - with high confidence
-
 - A system where individual features must release *without* a full redeployment of the entire system
-
 - An application developed by teams with expertise in different technology stacks
-
 - An application with components that must scale independently
 
 Smaller, less impactful line-of-business applications might fare well with a simple monolithic architecture hosted in a Cloud PaaS environment.
@@ -70,29 +66,17 @@ With the introduction behind, we now dive into a much more detailed look at clou
 ### References
 
 - [Cloud Native Computing Foundation](https://www.cncf.io/)
-
 - [.NET Microservices: Architecture for Containerized .NET applications](https://dotnet.microsoft.com/download/thank-you/microservices-architecture-ebook)
-
 - [Microsoft Azure Well-Architected Framework](/azure/architecture/framework/)
-
 - [Modernize existing .NET applications with Azure cloud and Windows Containers](https://dotnet.microsoft.com/download/thank-you/modernizing-existing-net-apps-ebook)
-
 - [Cloud Native Patterns by Cornelia Davis](https://www.manning.com/books/cloud-native-patterns)
-
 - [Cloud native applications: Ship faster, reduce risk, and grow your business](https://tanzu.vmware.com/cloud-native)
-
 - [Dapr documents](https://dapr.io/)
-
 - [Beyond the Twelve-Factor Application](https://content.pivotal.io/blog/beyond-the-twelve-factor-app)
-
 - [What is Infrastructure as Code](/devops/deliver/what-is-infrastructure-as-code)
-
 - [Uber Engineering's Micro Deploy: Deploying Daily with Confidence](https://www.uber.com/blog/micro-deploy-code/)
-
 - [How Netflix Deploys Code](https://www.infoq.com/news/2013/06/netflix/)
 
-- [Overload Control for Scaling WeChat Microservices](https://www.cs.columbia.edu/~ruigu/papers/socc18-final100.pdf)
-
 >[!div class="step-by-step"]
 >[Previous](definition.md)
 >[Next](introduce-eshoponcontainers-reference-app.md)
@@ -27,11 +27,11 @@ At the same time, business systems have also become increasingly complex with us
 
 Here are some companies who have implemented cloud-native techniques. Think about the speed, agility, and scalability they've achieved.
 
-| Company | Experience |
-| :-------- | :-------- |
-| [Netflix](https://www.infoq.com/news/2013/06/netflix/) | Has 600+ services in production. Deploys 100 times per day. |
-| [Uber](https://www.uber.com/blog/micro-deploy-code/) | Has 1,000+ services in production. Deploys several thousand times each week. |
-| [WeChat](https://www.cs.columbia.edu/~ruigu/papers/socc18-final100.pdf) | Has 3,000+ services in production. Deploys 1,000 times a day. |
+| Company  | Experience  |
+|:-------------------------------------------------------|:--------------------------------------------------------------|
+| [Netflix](https://www.infoq.com/news/2013/06/netflix/) | Has 600+ services in production. Deploys 100 times per day.  |
+| [Uber](https://www.uber.com/blog/micro-deploy-code/)  | Has 1,000+ services in production. Deploys several thousand times each week. |
+| WeChat  | Has 3,000+ services in production. Deploys 1,000 times a day. |
 
 As you can see, Netflix, Uber, and, WeChat expose cloud-native systems that consist of many independent services. This architectural style enables them to rapidly respond to market conditions. They instantaneously update small areas of a live, complex application, without a full redeployment. They individually scale services as needed.
 

@@ -96,7 +96,7 @@ This topic is continued with a couple of example walkthroughs for using OpenTele
 
 [.NET Aspire](/dotnet/aspire/get-started/aspire-overview) is a set of extensions to .NET to make it easy to create and work with distributed applications. One of the benefits of using .NET Aspire is that telemetry is built in, using the OpenTelemetry libraries for .NET. The default project templates for .NET Aspire contain a `ServiceDefaults` project, part of which is to setup and configure OTel. The Service Defaults project is referenced and initialized by each service in a .NET Aspire solution.
 
-The Service Defaults project template includes the OTel SDK, ASP.NET, HttpClient and Runtime Instrumentation packages, and those are configured in the [`Extensions.cs`](https://github.com/dotnet/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-servicedefaults/9.2/Extensions.cs) file. For exporting telemetry .NET Aspire includes the OTLP exporter by default so that it can provide telemetry visualization using the Aspire Dashboard.
+The Service Defaults project template includes the OTel SDK, ASP.NET, HttpClient and Runtime Instrumentation packages, and those are configured in the [`Extensions.cs`](https://github.com/dotnet/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-servicedefaults/9.3/Extensions.cs) file. For exporting telemetry .NET Aspire includes the OTLP exporter by default so that it can provide telemetry visualization using the Aspire Dashboard.
 
 The Aspire Dashboard is designed to bring telemetry observation to the local debug cycle, which enables developers to not only ensure that the applications are producing telemetry, but also use that telemetry to diagnose those applications locally. Being able to observe the calls between services is proving to be just as useful at debug time as in production. The .NET Aspire dashboard is launched automatically when you F5 the `AppHost` Project from Visual Studio or `dotnet run` the `AppHost` project.
 
@@ -114,8 +114,8 @@ Probably the easiest way to configure OTel for ASP.NET projects is to use the As
 
 The steps to use *ServiceDefaults* outside .NET Aspire are:
 
-- Add the *ServiceDefaults* project to the solution using Add New Project in Visual Studio, or use `dotnet new aspire-servicedefaults --output ServiceDefaults`
-- Reference the *ServiceDefaults* project from your ASP.NET application. In Visual Studio use "Add -> Project Reference" and select the *ServiceDefaults* project"
+- Add the *ServiceDefaults* project to the solution using Add New Project in Visual Studio, or use `dotnet new aspire-servicedefaults --output ServiceDefaults`.
+- Reference the *ServiceDefaults* project from your ASP.NET application. In Visual Studio use **Add** > **Project Reference** and select the *ServiceDefaults* project.
 - Call its OpenTelemetry setup function as part of your application builder initialization.
 
 ``` csharp

@@ -63,7 +63,6 @@ You might need to install [.NET dependencies](https://github.com/dotnet/core/blo
 
 ### Package managers
 
-- <https://formulae.brew.sh/cask/dotnet>
 - <https://formulae.brew.sh/cask/dotnet-sdk>
 - <https://ports.macports.org/port/dotnet-cli>
 - <https://search.nixos.org/packages?query=dotnet>

@@ -12,7 +12,7 @@ ms.date: 10/08/2024
 
 # What is .NET Upgrade Assistant?
 
-.NET Upgrade Assistant helps upgrade projects to newer versions of .NET, and analyzes your code to spot and fix potential incompatibilities. One focus of the tool is to help migrate a project from .NET Framework, .NET Core, or .NET, to the latest version of .NET. You use the extension or tool to upgrade entire .NET projects, or some aspect of the project, such migrating a configuration file from an older type to a newer type.
+.NET Upgrade Assistant helps upgrade projects to newer versions of .NET and analyzes your code to spot and fix potential incompatibilities. One focus of the tool is to help migrate a project from .NET Framework, .NET Core, or .NET, to the latest version of .NET. You use the extension or tool to upgrade entire .NET projects, or some aspect of the project, such migrating a configuration file from an older type to a newer type.
 
 .NET Upgrade Assistant is distributed as a Visual Studio extension or a command-line interface (CLI) tool.
 
@@ -52,7 +52,7 @@ One key feature of .NET Upgrade Assistant is designing upgrade extensions for yo
 
 Some products provide guidance on how to use .NET Upgrade Assistant.
 
-- [ASP.NET](/aspnet/core/migration/mvc)
+- [ASP.NET](/aspnet/core/migration/fx-to-core/tooling)
 - [Windows Presentation Foundation](/dotnet/desktop/wpf/migration/)
 - [Windows Forms](/dotnet/desktop/winforms/migration/)
 - [Universal Windows Platform](/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/upgrade-assistant)

@@ -22,8 +22,6 @@ Time values are measured in 100-nanosecond units called ticks. A particular date
 > [!NOTE]
 > If you're working with a ticks value that you want to convert to some other time interval, such as minutes or seconds, you should use the <xref:System.TimeSpan.TicksPerDay?displayProperty=nameWithType>, <xref:System.TimeSpan.TicksPerHour?displayProperty=nameWithType>, <xref:System.TimeSpan.TicksPerMinute?displayProperty=nameWithType>, <xref:System.TimeSpan.TicksPerSecond?displayProperty=nameWithType>, or <xref:System.TimeSpan.TicksPerMillisecond?displayProperty=nameWithType> constant to perform the conversion. For example, to add the number of seconds represented by a specified number of ticks to the <xref:System.DateTime.Second> component of a <xref:System.DateTime> value, you can use the expression `dateValue.Second + nTicks/Timespan.TicksPerSecond`.
 
-You can view the source for the entire set of examples from this article in either [Visual Basic](https://github.com/dotnet/dotnet-api-docs/tree/main/snippets/visualbasic/System.DateTime/), [F#](https://github.com/dotnet/dotnet-api-docs/tree/main/snippets/fsharp/System.DateTime/), or [C#](https://github.com/dotnet/dotnet-api-docs/tree/main/snippets/csharp/System.DateTime/).
-
 > [!NOTE]
 > An alternative to the <xref:System.DateTime> structure for working with date and time values in particular time zones is the <xref:System.DateTimeOffset> structure. The <xref:System.DateTimeOffset> structure stores date and time information in a private <xref:System.DateTime> field and the number of minutes by which that date and time differs from UTC in a private <xref:System.Int16> field. This makes it possible for a <xref:System.DateTimeOffset> value to reflect the time in a particular time zone, whereas a <xref:System.DateTime> value can unambiguously reflect only UTC and the local time zone's time. For a discussion about when to use the <xref:System.DateTime> structure or the <xref:System.DateTimeOffset> structure when working with date and time values, see [Choosing Between DateTime, DateTimeOffset, TimeSpan, and TimeZoneInfo](../../standard/datetime/choosing-between-datetime.md).
 

@@ -39,17 +39,17 @@ Create a **C# console application** called "RestaurantViolations".
 
 ## Prepare and understand the data
 
-> The data set used to train and evaluate the machine learning model is originally from the [San Francisco Department of Public Health Restaurant Safety Scores](https://www.sfdph.org/dph/EH/Food/score/default.asp). For convenience, the dataset has been condensed to only include the columns relevant to train the model and make predictions. Visit the following website to learn more about the [dataset](https://data.sfgov.org/Health-and-Social-Services/Restaurant-Scores-LIVES-Standard/pyih-qa8i?row_index=0).
+> The data set used to train and evaluate the machine learning model is originally from the San Francisco Department of Public Health Restaurant Safety Scores. For convenience, the dataset has been condensed to only include the columns relevant to train the model and make predictions. Visit the following website to learn more about the [dataset](https://data.sfgov.org/Health-and-Social-Services/Restaurant-Scores-LIVES-Standard/pyih-qa8i?row_index=0).
 
 [Download the Restaurant Safety Scores dataset](https://github.com/dotnet/machinelearning-samples/raw/main/samples/modelbuilder/MulticlassClassification_RestaurantViolations/RestaurantScores.zip) and unzip it.
 
 Each row in the dataset contains information regarding violations observed during an inspection from the Health Department and a risk assessment of the threat those violations present to public health and safety.
 
-| InspectionType | ViolationDescription | RiskCategory |
-| --- | --- | --- |
-| Routine - Unscheduled | Inadequately cleaned or sanitized food contact surfaces | Moderate Risk |
-| New Ownership | High risk vermin infestation | High Risk |
-| Routine - Unscheduled | Wiping cloths not clean or properly stored or inadequate sanitizer | Low Risk |
+| InspectionType  | ViolationDescription  | RiskCategory  |
+|-----------------------|--------------------------------------------------------------------|---------------|
+| Routine - Unscheduled | Inadequately cleaned or sanitized food contact surfaces  | Moderate Risk |
+| New Ownership  | High risk vermin infestation  | High Risk  |
+| Routine - Unscheduled | Wiping cloths not clean or properly stored or inadequate sanitizer | Low Risk  |
 
 - **InspectionType**: the type of inspection. This can either be a first-time inspection for a new establishment, a routine inspection, a complaint inspection, and many other types.
 - **ViolationDescription**: a description of the violation found during inspection.

@@ -47,7 +47,7 @@ items:
  expanded: true
  items:
  - name: ASP.NET
- href: /aspnet/core/migration/mvc
+ href: /aspnet/core/migration/fx-to-core/tooling
  - name: Windows Presentation Foundation
  href: /dotnet/desktop/wpf/migration/
  - name: Windows Forms

@@ -11,7 +11,7 @@ items:
  - name: .NET 10
  href: ../core/whats-new/dotnet-10/overview.md?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: C# 13
- href: /csharp/whats-new/csharp-13?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
+ href: /dotnet/csharp/whats-new/csharp-13?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: ASP.NET Core 10.0
  href: /aspnet/core/release-notes/aspnetcore-10.0?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: EF Core 10
@@ -21,7 +21,7 @@ items:
  - name: .NET 9
  href: ../core/whats-new/dotnet-9/overview.md?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: C# 12
- href: /csharp/whats-new/csharp-12?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
+ href: /dotnet/csharp/whats-new/csharp-12?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: ASP.NET Core 9.0
  href: /aspnet/core/release-notes/aspnetcore-9.0?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: .NET MAUI 9
@@ -33,7 +33,7 @@ items:
  - name: .NET 8
  href: ../core/whats-new/dotnet-8/overview.md?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: C# 11
- href: /csharp/whats-new/csharp-11?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
+ href: /dotnet/csharp/whats-new/csharp-11?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: ASP.NET Core 8.0
  href: /aspnet/core/release-notes/aspnetcore-8.0?toc=/dotnet/whats-new/toc.json&bc=/dotnet/breadcrumb/toc.json
  - name: Windows Forms (.NET 8)