fix broken links

Author: gewarren

.openpublishing.redirection.visual-basic.json

@@ -255,6 +255,10 @@
             "source_path_from_root": "/docs/visual-basic/language-reference/error-messages/class-classname-cannot-be-found.md",
             "redirect_url": "/dotnet/visual-basic/language-reference/error-messages/bc31098"
         },
+        {
+            "source_path_from_root": "/docs/visual-basic/language-reference/error-messages/late-bound-resolution;-runtime-errors-could-occur.md",
+            "redirect_url": "/dotnet/visual-basic/language-reference/error-messages/late-bound-resolution-runtime-errors-could-occur"
+        },
         {
             "source_path_from_root": "/docs/visual-basic/language-reference/queries/queries.md",
             "redirect_url": "/dotnet/visual-basic/language-reference/queries/index",

docs/core/diagnostics/observability-with-otel.md

@@ -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/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.0/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.
 

docs/visual-basic/language-reference/error-messages/late-bound-resolution;-runtime-errors-could-occur.md renamed to docs/visual-basic/language-reference/error-messages/late-bound-resolution-runtime-errors-could-occur.md

@@ -1104,7 +1104,7 @@ items:
     - name: Lambda expressions are not valid in the first expression of a 'Select Case' statement
       href: language-reference/error-messages/lambda-expressions-are-not-valid-in-the-first-expression-of-select-case.md
     - name: Late bound resolution; runtime errors could occur
-      href: language-reference/error-messages/late-bound-resolution;-runtime-errors-could-occur.md
+      href: language-reference/error-messages/late-bound-resolution-runtime-errors-could-occur.md
     - name: Latebound overload resolution cannot be applied to '<procedurename>' because the accessing instance is an interface type
       href: language-reference/error-messages/latebound-overload-resolution-cannot-be-applied.md
     - name: Leading '.' or '!' can only appear inside a 'With' statement