Fix 30649

.config/dotnet-tools.json

@@ -3,28 +3,39 @@
   "isRoot": true,
   "tools": {
     "cake.tool": {
-      "version": "2.3.0",
+      "version": "4.0.0",
       "commands": [
         "dotnet-cake"
-      ]
+      ],
+      "rollForward": false
     },
     "powershell": {
       "version": "7.4.0",
       "commands": [
         "pwsh"
-      ]
+      ],
+      "rollForward": false
     },
     "api-tools": {
       "version": "1.3.5",
       "commands": [
         "api-tools"
-      ]
+      ],
+      "rollForward": false
     },
     "microsoft.dotnet.xharness.cli": {
-      "version": "9.0.0-prerelease.23577.1",
+      "version": "9.0.0-prerelease.25317.3",
       "commands": [
         "xharness"
-      ]
+      ],
+      "rollForward": false
+    },
+    "androidsdk.tool": {
+      "version": "0.19.0",
+      "commands": [
+        "android"
+      ],
+      "rollForward": false
     }
   }
 }

.editorconfig

@@ -29,6 +29,7 @@ dotnet_diagnostic.CA1307.severity = error
 dotnet_diagnostic.CA1309.severity = error
 dotnet_diagnostic.CA1311.severity = error
 dotnet_diagnostic.CA1815.severity = error
+dotnet_diagnostic.CA1825.severity = error
 
 # nullability checks
 
@@ -66,6 +67,10 @@ csharp_style_var_for_built_in_types = true:none
 csharp_style_var_when_type_is_apparent = true:none
 csharp_style_var_elsewhere = false:none
 
+# Namespace preference (prefer file-scoped namespaces)
+csharp_style_namespace_declarations = file_scoped
+dotnet_diagnostic.IDE0161.severity = suggestion
+
 # use language keywords instead of BCL types
 dotnet_style_predefined_type_for_locals_parameters_members = true:suggestion
 dotnet_style_predefined_type_for_member_access = true:suggestion
@@ -105,6 +110,7 @@ dotnet_naming_style.camel_case_underscore_style.capitalization = camel_case
 dotnet_sort_system_directives_first = true
 csharp_preserve_single_line_blocks = true
 csharp_preserve_single_line_statements = false
+csharp_prefer_braces = true:suggestion
 
 # Expression-level preferences
 dotnet_style_object_initializer = true:suggestion

.github/CODEOWNERS

@@ -1,10 +1 @@
 *       @dotnet/dotnet-maui-reviewers
-
-# Tizen (this probably doesn't work since these do not have write access
-**/Tizen @rookiejava @myroot @shyunmin @sung-su @JoonghyunCho
-*.tizen.cs @rookiejava @myroot @shyunmin @sung-su @JoonghyunCho
-*.Tizen.cs @rookiejava @myroot @shyunmin @sung-su @JoonghyunCho
-
-# Blazor Desktop
-/src/BlazorWebView/                                     @dotnet/dotnet-maui-blazor-eng
-/src/Templates/src/templates/maui-blazor/               @dotnet/dotnet-maui-blazor-eng

.github/CONTRIBUTING.md

@@ -35,6 +35,24 @@ Please refer to our [Pull Request template](PULL_REQUEST_TEMPLATE.md).
 
 Please check the "Allow edits from maintainers" checkbox on your pull request. This allows us to quickly make minor fixes and resolve conflicts for you.
 
+### Performance-related Changes
+
+Performance improvements can be tricky to get right, and can sometimes have unexpected consequences and impact code readability. If you're considering a performance-related change, here are a few things to keep in mind:
+
+1. **Profile a real-world application**: Before making any performance-related changes, profile a real-world application (or at least a sample project) to understand where the bottlenecks are. This will help you understand if your change is actually improving performance, and if it's improving the right thing. We want to avoid micro-optimizations that don't actually improve real-world .NET MAUI applications.
+
+See [our profiling wiki](https://aka.ms/profile-maui) for instructions on how to profile a .NET MAUI application.
+
+2. **Benchmark your change**: If you're making a performance-related change, please include benchmarks in your pull request. This will help us understand the impact of your change, and will help us avoid performance regressions in the future.
+
+Provide before & after numbers using BenchmarkDotNet where possible. See our existing [BenchmarkDotNet project](../src/Core/tests/Benchmarks/) for examples.
+
+If a BenchmarkDotNet test case is not possible, share before & after profiling information from Visual Studio, `dotnet-trace`, etc. Keep in mind that sampling profilers can be inaccurate, so someone from the .NET MAUI team may need to reproduce your results before merging your change.
+
+3. **Preserve existing behavior**: If you're making a performance-related change, please make sure that you're not changing the behavior of the code. For example, if you're changing the implementation of a method, make sure that the new implementation returns the same results as the old implementation. In some cases, you may need to add new unit tests to ensure that the behavior of the code hasn't changed.
+
+4. **Avoid impacting readability**: Performance-related changes can sometimes make code harder to read and understand. In many cases, it will be worth it if the payoff is significant, but please be mindful of the trade-offs. Write code comments and unit tests to help others understand the code in the future.
+
 ## Proposals/Enhancements/Suggestions
 
 To propose a change or new feature, open an issue using the [Feature request template](https://github.com/dotnet/maui/issues/new?assignees=&labels=proposal-open%2C+t%2Fenhancement+➕&template=feature_request.md&title=[Enhancement]+YOUR+IDEA!). You may also use the [Spec template](https://github.com/dotnet/maui/issues/new?assignees=&labels=proposal-open%2C+t%2Fenhancement+➕&template=spec.md&title=[Spec]++) if you have an idea of what the API should look like. Be sure to also browse current issues and [discussions](https://github.com/dotnet/maui/discussions) that may be related to what you have in mind.