Auto-connection request for dotnet-runtime-110 content interface

store-requests privileged-interfaces
1
  • name: dotnet-runtime-110
  • description: This is the content snap that provides the .NET 11 runtime binaries for application snaps that need it through the content interface.
  • snapcraft: snapcraft.yaml
  • upstream: GitHub - dotnet/dotnet: Home of .NET's Virtual Monolithic Repository which includes all the code needed to build the .NET SDK. · GitHub
  • upstream-relation: I work in the Runtimes team at Canonical, maintaining the .NET runtime and SDK deb packages and snaps. The .NET snaps in the Snap Store are owned by Canonical.
  • interfaces:
    • dotnet-runtime:
      • request-type: auto-connection
      • reasoning: Apps that depend on the .NET Runtime to run can use these content snaps as providers of the runtime. The goal with the runtime content interface auto-connecting is to make the snap experience more seamless for .NET applications by removing the need for non-technical users to run snap connect after installing applications for them to work properly.

Note: The following .NET runtime content snaps, which are also maintained by us, already have the content interface auto-connection enabled, as previously requested:

  • dotnet-runtime-100
  • dotnet-runtime-90
  • dotnet-runtime-80
  • dotnet-runtime-70
  • dotnet-runtime-60
2

This request has been added to the queue for review by the @reviewers team.

3

Given the context and previous requests, this is a +1 (#voteFor) from me for granting content interface auto-connect to the dotnet-runtime-110 snap.

thanks

4

Hey folks,

I agree this global auto-connection makes sense as for the previous versions of dotnet. +1 from me!

5

Since we have already granted a similar request for the dotnet-runtime snaps, I am expediting this request and proceeding with granting it:

+2 in favor, 0 against. The auto-connection of the content interface to the dotnet-runtime-110 snap has now been granted and is now live. (#approved)

1 Like