NuGet | local nuget repository for hosting modules | Runtime Evironment library

From Agent pool - Change Agent Specification from Window-Latest to Window-2019 ,It seems MS has done some changes in default agent

Image

Since dotnet restore and dotnet build are wrappers around dotnet msbuild, you can use all MSBuild switches to change behavior of build system.

Here we need to set target framework, which can be done by

• setting property in project file: net5.0

OR

• setting property through command line docs: dotnet restore -p:TargetFramework=net5.0

OR

• setting environment variable which is not recommended (by me)

Apparently I had BILLING permissions set in my manifest. Removing these fixed the issue.

You can do this by right-clicking the project --> Properties --> Android Manifest --> Searching for BILLING under "Required Permissions" and unchecking it

Alternatively, open AndroidManifest.xml and delete the line

After countless hours working on this, it seems that ultimately the issue was that our internal Web Application Firewall was blocking some part of the transfer of artefacts to the server, or the response back from it. With the WAF reconfigured not to block traffic from the machine running the GitLab Runner, the artefacts are successfully uploaded and the job succeeds.

This would have been significantly easier to diagnose if the logging from GitLab was better. As per my comment on this issue, it should be possible to see the content of the response from the GitLab server after uploading artefacts, even when the response code is 200.

What's strange - and made diagnosing the issue even harder - is that when I worked through the issue with the admin of our GitLab instance, digging through logs and running it in debug mode, the artefact upload process was uploading something successfully. We could see, for example, the GitLab Runner's log had been uploaded to the server. Clearly the WAF's blocking was selective and didn't block everything in both directions.

You need to execute playwright install in the folder that contains the csproj or use -p to specify the project file

have you tried dotnet build? that usually forces auto resolving of dependencies!

I've also faced similar issues in recent days after the final release of 2022.

• Updated Answer This can be resolved using MSBuild task instead, as the collogues mentioned below. However, in my case this still lead to the same error. After investigating the pipeline. The root cause has been identified: Both in MSBuild@1 and XamariniOS@2 tasks you should target the specific iOS Project and not the solution file, like so:

" - task: MSBuild@1 inputs: solution: 'PathToIosProject/myproject.iOS.csproj' configuration: '$(BuildConfiguration)' msbuildArguments: /t:restore

" - task: XamariniOS@2 inputs: solutionFile: PathToIosProject/myproject.iOS.csproj' configuration: '$(BuildConfiguration)' packageApp: true signingIdentity: $(APPLE_CERTIFICATE_SIGNING_IDENTITY)

• Old Answer

We have managed to resolve the issue. The root cause of it seems to be an update to the mono framework in the MacOS pipeline build agent. In order to fix it, we need a script for downloading and installing an older version of the mono framework as a first step of the build pipeline like so: link to the pipeline tasks photo

This is the code of the bash scrip used in the task:

#!/bin/bash set -ex

MONO_MACOS_PKG_DOWNLOAD_URL='https://download.mono-project.com/archive/6.12.0/macos-10-universal/MonoFramework-MDK-6.12.0.100.macos10.xamarin.universal.pkg'

mkdir -p /tmp/mono-install cd /tmp/mono-install

mono --version

wget -q -O ./mono-installer.pkg "$MONO_MACOS_PKG_DOWNLOAD_URL"

sudo installer -pkg ./mono-installer.pkg -target /

mono --version

ls -alh /Library/Frameworks/Mono.framework/Versions/Current

As mentioned by the comment on the question and on this site

https://github.com/dotnet/Scaffolding/issues/1713

Removing the nuget package Microsoft.AspNetCore.Identity from all projects in the relevant solution solves the problem.

In many cases (also in mine) its enough to reference the nuget package Microsoft.AspNetCore.Identity.EntityFrameworkCore

So my problem was with the way Azure was building the RCL solution and packaging the RCL in a nuget package.

I had to update my build YML to use 2022 image, and v6.0 of .NET and nuget:

Changed