Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: dotnet/android
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 16bb23264f
Choose a base ref
...
head repository: dotnet/android
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 097742b3d0
Choose a head ref
  • 3 commits
  • 44 files changed
  • 2 contributors

Commits on Jan 13, 2026

  1. [build] net11.0 target framework (#10664)

    Changes: dotnet/dotnet@67ecf9e...db3b742
    
    Bump to dotnet/dotnet@db3b742425
    
    - **Dependency Updates**:
      - From [11.0.0-alpha.1.26055.114 to 11.0.0-alpha.1.26060.102][1]
         - Microsoft.NET.Workload.Mono.ToolChain.Current.Manifest-11.0.100-alpha.1
         - Microsoft.NET.ILLink
         - Microsoft.NETCore.App.Ref
      - From [11.0.0-beta.26055.114 to 11.0.0-beta.26060.102][1]
         - Microsoft.DotNet.Build.Tasks.Feed
      - From [0.11.5-alpha.26055.114 to 0.11.5-alpha.26060.102][1]
         - Microsoft.DotNet.Cecil
      - From [11.0.100-alpha.1.26055.114 to 11.0.100-alpha.1.26060.102][1]
         - Microsoft.NET.Sdk
         - Microsoft.NET.Workload.Emscripten.Current.Manifest-11.0.100-alpha.1
      - From [11.0.100-alpha.26055.114 to 11.0.100-alpha.26060.102][1]
         - Microsoft.TemplateEngine.Authoring.Tasks
    
    This updates the codebase to target `net11.0` as the default,
    including support for `net11.0-android`.
    
    **Target framework and SDK updates:**
    
    * Set the default target framework to `net11.0` and the stable target
      to `net10.0` in `Directory.Build.props` and pipeline variables.
    
    * Added constants for latest and previous .NET target frameworks in
      `XABuildConfig.cs.in`.
    
    * Updated `PREPARE_NET_FX` in `Makefile` and improved workload
      manifest handling for `net10` in `xaprepare`.
    
    **CI and build improvements:**
    
    * Updated CI YAML templates to only run
      `prepare-external-git-dependencies` for non-forked PRs.
    
    * Added NuGet package source for dotnet/runtime 9.0.12.
    
    **Documentation and templates:**
    
    * Updated documentation and issue templates to reference
      `net11.0-android` and use the new default target framework in
      examples.
    
    **Other configuration updates:**
    
    * Set `TargetsCurrent=true` in `Directory.Build.props` as a temporary
      workaround for a known SDK issue.
    
    * Updated the default .NET SDK version for CI to 10.0.
    
    [1]: dotnet/dotnet@67ecf9e...db3b742
    jonathanpeppers authored Jan 13, 2026
    Configuration menu
    Copy the full SHA
    a2c2045 View commit details
    Browse the repository at this point in the history
  2. [build] Disable debug spew from the localizer (#10673)

    Local builds would generate hundreds (nearly 700) of messages similar to these:
    
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //$schema
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //$schema
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //$schema
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //$schema
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //$schema
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //$schema
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //author
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //author
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //author
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //author
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //classifications
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //classifications
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //classifications
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //identity
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //author
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //author
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //name
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //classifications
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: The following element in the template.json will not be included in the localizations because it does not match any of the rules for localizable elements: //classifications
        Microsoft.TemplateEngine.TemplateLocalizer.Core.TemplateStringExtractor: Adding into localizable strings: //description
    
    Disable the localizer for local builds by default.
    
    In order to rebuild them it is necessary to build the templates project in 
    one of the following ways:
    
       * On Unix systems run `make LOCALIZE_TEMPLATES=true prepare all` (the `prepare` parameter
         can be omitted if it was ran previously)
       * On all systems run `dotnet-local.sh -p:LocalizeTemplates=true -t:ConfigureLocalWorkload build-tools/create-packs/Microsoft.Android.Sdk.proj`
    grendello authored Jan 13, 2026
    Configuration menu
    Copy the full SHA
    3595451 View commit details
    Browse the repository at this point in the history

Commits on Jan 14, 2026

  1. [build] fix generate and publish BAR manifest step (#10685)

    This failed with:
    
        Microsoft.NET.TargetFrameworkInference.targets(188,5): error NETSDK1045:
        The current .NET SDK does not support targeting .NET 11.0.
        Either target .NET 10.0 or lower, or use a version of the .NET SDK that supports .NET 11.0.
        Download the .NET SDK from https://aka.ms/dotnet/download
    
    This step doesn't *need* to use .NET 11, so...
    
    I think we can use `$(DotNetStableTargetFramework)` in this project
    to avoid this problem for now.
    jonathanpeppers authored Jan 14, 2026
    Configuration menu
    Copy the full SHA
    097742b View commit details
    Browse the repository at this point in the history
Loading