Tags: dotnet/dotnet
Tags
Merged PR 61429: Update MessagePack #### AI description (iteration 1) #### PR Classification Code quality improvement and modernization, including the addition of performance telemetry instrumentation. #### PR Summary This pull request updates the MessagePack-CSharp submodule, primarily enhancing the dynamic formatter generation code with telemetry support and null-safety improvements. - Added `MessagePackEventSource` telemetry tracking around dynamic formatter generation in `DynamicObjectResolver.cs` to monitor performance - Improved null-safety with nullable reference type annotations (e.g., `type.FullName!`, `object?` return types) - Refactored custom formatter handling logic to use pattern matching checks (`is object formatter`) - Removed obsolete public API tracking file `net5.0/PublicAPI.Shipped.txt` <!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->
Merged PR 61373: [internal/release/10.0.301] Update dependencies from… … dnceng/internal/dotnet-dotnet This pull request updates the following dependencies [marker]: <> (Begin:3ed06ccc-72db-4136-8a02-c9db8e46195c) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet - **Subscription**: [3ed06ccc-72db-4136-8a02-c9db8e46195c](https://maestro.dot.net/subscriptions?search=3ed06ccc-72db-4136-8a02-c9db8e46195c) - **Build**: [20260520.8](https://dev.azure.com/dnceng/internal/_build/results?buildId=2979997) ([315276](https://maestro.dot.net/channel/8858/azdo:dnceng:internal:dotnet-dotnet/build/315276)) - **Date Produced**: May 20, 2026 11:17:18 PM UTC - **Commit**: [e324605](https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet?_a=history&version=GCe3246058490de40dc0dfd381bb8904c115a3a67a) - **Branch**: [refs/heads/internal/release/10.0.109](https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet?version=GBrefs/heads/internal/release/10.0.109) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - 📂 `root` - From [10.0.0-beta.26268.115 to 10.0.0-beta.26270.108][1] - Microsoft.DotNet.Build.Manifest - From [10.0.109-servicing.26268.115 to 10.0.109-servicing.26270.108][1] - Microsoft.NET.Sdk - From [10.0.9 to 10.0.9][1] - Microsoft.NETCore.App.Ref - From [10.0.9-servicing.26268.115 to 10.0.9-servicing.26270.108][1] - Microsoft.NETCore.Platforms - 📂 `src/roslyn` - From [2.0.9 to 2.0.9][1] - System.CommandLine - 📂 `src/scenario-tests` - From [2.0.9 to 2.0.9][1] - System.CommandLine - 📂 `src/sdk` - From [10.0.9-servicing.26268.115 to 10.0.9-servicing.26270.108][1] - dotnet-dev-certs - dotnet-user-jwts - dotnet-user-secrets - Microsoft.AspNetCore.Analyzers - Microsoft.AspNetCore.App.Ref.Internal - Microsoft.AspNetCore.Components.SdkAnalyzers - Microsoft.AspNetCore.DeveloperCertificates.XPlat - Microsoft.AspNetCore.Mvc.Analyzers - Microsoft.AspNetCore.Mvc.Api.Analyzers - Microsoft.Dotnet.WinForms.ProjectTemplates - Microsoft.DotNet.Wpf.ProjectTemplates - Microsoft.NET.HostModel - Microsoft.NET.Sdk.WindowsDesktop - Microsoft.NETCore.Platforms - Microsoft.WindowsDesktop.App.Internal - From [10.0.9 to 10.0.9][1] - Microsoft.AspNetCore.App.Ref - Microsoft.AspNetCore.Authentication.Facebook - Microsoft.AspNetCore.Authentication.Google - Microsoft.AspNetCore.Authentication.MicrosoftAccount - Microsoft.AspNetCore.Authorization - Microsoft.AspNetCore.Components - Microsoft.AspNetCore.Components.Analyzers - Microsoft.AspNetCore.Components.Forms - Microsoft.AspNetCore.Components.Web - Microsoft.AspNetCore.Components.WebAssembly - Microsoft.AspNetCore.Components.WebAssembly.Server - Microsoft.AspNetCore.Components.WebView - Microsoft.AspNetCore.Metadata - Microsoft.AspNetCore.TestHost - Microsoft.Bcl.AsyncInterfaces - Mic...
Merged PR 61428: Update MessagePack #### AI description (iteration 1) #### PR Classification Submodule update to integrate the latest version of MessagePack-CSharp library. #### PR Summary This pull request updates the MessagePack-CSharp submodule, incorporating improvements to dynamic formatter generation with enhanced telemetry and null-safety annotations. - `DynamicObjectResolver.cs`: Added `MessagePackEventSource` instrumentation to track formatter dynamic generation lifecycle with start/stop events - `DynamicObjectResolver.cs`: Enhanced null-safety with nullable reference type annotations (e.g., `type.FullName!`, `object?` returns) - `DynamicObjectResolver.cs`: Refactored custom formatter lookup to use pattern matching for cleaner null checks - Removed obsolete `net5.0/PublicAPI.Shipped.txt` file as part of the submodule update <!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->
Merged PR 61331: Render Router's NotFoundPage through the <Found> tem… …plate Backport of https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet/pullrequest/61324. NotFoundPage feature was added in net10 in dotnet/aspnetcore#60970 . If its value is set in the Router, it will be rendered on NavigationManager.NotFound() call or NavigationManager.Navigate("non-existing-path"). Originally it was rendered with bare <RouteView>, creating a different logical path for rendering than other pages that go through <Found> fragment. This meant that <AuthorizeRouteView> inside <Found> (and other wrappers, such as custom layouts or other route-view decorators) was never applied. As a result, NotFoundPage that carried [Authorize] attribute behaved as if that attribute did not exist on it. Fix: Instead of "manual" rendering setup, use <Found> to render NotFoundPage. Tested: E2E for not found page with [Authorize] -> expect NotAuthorize content. Passes locally. Updated unit test that used to expect bare <RouteView>. Passes locally. Manual tests of Component.TestServer app with the change. ---- #### AI description (iteration 1) #### PR Classification Bug fix to ensure the Router's NotFoundPage is rendered through the `<Found>` template instead of directly through `RouteView`. #### PR Summary This PR changes how the Router component renders the NotFoundPage by delegating to the `<Found>` template, enabling proper rendering of authorized/protected not-found pages through `AuthorizeRouteView`. - `Router.cs`: Modified to render NotFoundPage through the `Found` template instead of directly instantiating `RouteView` - `App.razor`: Added support for `useAuthorizedNotFoundPage` query parameter and new router configuration with `AuthorizeRouteView` to handle authorized not-found scenarios - `AuthorizedNotFoundPage.razor`: Added new test page with `[Authorize]` attribute to verify protected not-found pages render correctly - `NoInteractivityTest.cs`: Added test to verify anonymous users see "Not authorized" content when accessing authorized not-found pages - `RouterTest.cs`: Updated assertion to verify NotFoundPage is rendered through the `<Found>` template <!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->
Merged PR 61331: Render Router's NotFoundPage through the <Found> tem… …plate Backport of https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet/pullrequest/61324. NotFoundPage feature was added in net10 in dotnet/aspnetcore#60970 . If its value is set in the Router, it will be rendered on NavigationManager.NotFound() call or NavigationManager.Navigate("non-existing-path"). Originally it was rendered with bare <RouteView>, creating a different logical path for rendering than other pages that go through <Found> fragment. This meant that <AuthorizeRouteView> inside <Found> (and other wrappers, such as custom layouts or other route-view decorators) was never applied. As a result, NotFoundPage that carried [Authorize] attribute behaved as if that attribute did not exist on it. Fix: Instead of "manual" rendering setup, use <Found> to render NotFoundPage. Tested: E2E for not found page with [Authorize] -> expect NotAuthorize content. Passes locally. Updated unit test that used to expect bare <RouteView>. Passes locally. Manual tests of Component.TestServer app with the change. ---- #### AI description (iteration 1) #### PR Classification Bug fix to ensure the Router's NotFoundPage is rendered through the `<Found>` template instead of directly through `RouteView`. #### PR Summary This PR changes how the Router component renders the NotFoundPage by delegating to the `<Found>` template, enabling proper rendering of authorized/protected not-found pages through `AuthorizeRouteView`. - `Router.cs`: Modified to render NotFoundPage through the `Found` template instead of directly instantiating `RouteView` - `App.razor`: Added support for `useAuthorizedNotFoundPage` query parameter and new router configuration with `AuthorizeRouteView` to handle authorized not-found scenarios - `AuthorizedNotFoundPage.razor`: Added new test page with `[Authorize]` attribute to verify protected not-found pages render correctly - `NoInteractivityTest.cs`: Added test to verify anonymous users see "Not authorized" content when accessing authorized not-found pages - `RouterTest.cs`: Updated assertion to verify NotFoundPage is rendered through the `<Found>` template <!-- GitOpsUserAgent=GitOps.Apps.Server.pullrequestcopilot -->
Merged PR 60612: [internal/release/10.0.300] Update dependencies from… … dnceng/internal/dotnet-dotnet This pull request updates the following dependencies [marker]: <> (Begin:a21b3713-a05f-4ed2-9cfe-d77ce2b0bccf) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet - **Subscription**: [a21b3713-a05f-4ed2-9cfe-d77ce2b0bccf](https://maestro.dot.net/subscriptions?search=a21b3713-a05f-4ed2-9cfe-d77ce2b0bccf) - **Build**: [20260429.19](https://dev.azure.com/dnceng/internal/_build/results?buildId=2963706) ([312518](https://maestro.dot.net/channel/8858/azdo:dnceng:internal:dotnet-dotnet/build/312518)) - **Date Produced**: April 30, 2026 6:57:34 AM UTC - **Commit**: [94ea826](https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet?_a=history&version=GC94ea82652cdd4e0f8046b5bd5becbd11461482ca) - **Branch**: [refs/heads/internal/release/10.0.108](https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet?version=GBrefs/heads/internal/release/10.0.108) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - 📂 `root` - From [10.0.0-beta.26219.105 to 10.0.0-beta.26229.119][2] - Microsoft.DotNet.Build.Manifest - From [10.0.108-servicing.26224.110 to 10.0.108-servicing.26229.119][3] - Microsoft.NET.Sdk - From [10.0.8 to 10.0.8][3] - Microsoft.NETCore.App.Ref - From [10.0.8-servicing.26224.110 to 10.0.8-servicing.26229.119][3] - Microsoft.NETCore.Platforms - 📂 `src/roslyn` - From [2.0.8 to 2.0.8][3] - System.CommandLine - 📂 `src/scenario-tests` - From [2.0.8 to 2.0.8][3] - System.CommandLine - 📂 `src/sdk` - From [10.0.8-servicing.26224.110 to 10.0.8-servicing.26229.119][3] - dotnet-dev-certs - dotnet-user-jwts - dotnet-user-secrets - Microsoft.AspNetCore.Analyzers - Microsoft.AspNetCore.App.Ref.Internal - Microsoft.AspNetCore.Components.SdkAnalyzers - Microsoft.AspNetCore.DeveloperCertificates.XPlat - Microsoft.AspNetCore.Mvc.Analyzers - Microsoft.AspNetCore.Mvc.Api.Analyzers - Microsoft.Dotnet.WinForms.ProjectTemplates - Microsoft.DotNet.Wpf.ProjectTemplates - Microsoft.NET.HostModel - Microsoft.NET.Sdk.WindowsDesktop - Microsoft.NETCore.Platforms - Microsoft.WindowsDesktop.App.Internal - From [10.0.8 to 10.0.8][3] - Microsoft.AspNetCore.App.Ref - Microsoft.AspNetCore.Authentication.Facebook - Microsoft.AspNetCore.Authentication.Google - Microsoft.AspNetCore.Authentication.MicrosoftAccount - Microsoft.AspNetCore.Authorization - Microsoft.AspNetCore.Components - Microsoft.AspNetCore.Components.Analyzers - Microsoft.AspNetCore.Components.Forms - Microsoft.AspNetCore.Components.Web - Microsoft.AspNetCore.Components.WebAssembly - Microsoft.AspNetCore.Components.WebAssembly.Server - Microsoft.AspNetCore.Components.WebView - Microsoft.AspNetCore.Metadata - Microsoft.AspNetCore.TestHost - Microsoft.Bcl.AsyncInterfaces - M...
PreviousNext