Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BMBF 2 BMBF 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Unicorns
  • BMBF 2BMBF 2
  • Issues
  • #3
Closed
Open
Created Feb 02, 2022 by Unicorn 12@Unicorn12Maintainer

Better strategy for fixing ASP.NET core runtime pack restoring

Currently, we use a hack where we invoke nuget.exe directly to install the Microsoft.AspNetCore.App.Runtime.linux-arm64 package.

This package is necessary in order to build our project for arm64-v8a with ASP.NET core, however due to some quirks with the net6.0-android target, it won't restore it automatically.

Invoking nuget manually isn't ideal as it requires nuget.exe to be available on PATH (which is not the case in a standard installation of .NET 6, as it only includes the necessary DLLs for restoring nuget packages with msbuild).

Assignee
Assign to
Time tracking