Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Use the latest Nuget Tool version for .NET 6


How can I use the latest version of the nuget tool when restoring the packages of a .NET 6 project? I noticed it is using old version that is preventing to restore successfully all my project packages.

Any hint is always welcome, please.

btw, On Azure DevOps, I got recommended to use:

- task: NuGetToolInstaller@1
However, I don't know how to use it on Bitbucket Pipelines.
Thanks in advance,

1 answer

1 accepted

0 votes
Answer accepted
Caroline R Atlassian Team Mar 03, 2022

Hi, Victor, thank you for reaching out to Atlassian Community.

In order to properly assist you, could you please share the following information with us?

  • What build image are you using?

  • Which Nuget are you using? 

  • What error/behavior are you getting? 

Thank you!

Kind regards,

Thanks @Caroline R  for your response.

The bitbucket-pipelines.yml I'm using is the following:

image: microsoft/dotnet:sdk




- step:

name: Build


- dotnetcore


- dotnet restore src/solution_name.sln

- dotnet build src/solution_name.sln --no-restore --configuration Release

The error, I'm getting is:

Images used:
build :
+ dotnet restore src/solution_name.sln
/opt/atlassian/pipelines/agent/build/src/project/project_name.csproj : error NU1202: Package MVCCaching.Kentico.Core 13.0.2 is not compatible with net60 (.NETFramework,Version=v6.0). Package MVCCaching.Kentico.Core 13.0.2 supports: netcoreapp3.1 (.NETCoreApp,Version=v3.1) [/opt/atlassian/pipelines/agent/build/src/solution_name.sln]
Restore failed in 1.25 sec for /opt/atlassian/pipelines/agent/build/src/project/project_name.csproj.
/opt/atlassian/pipelines/agent/build/src/project2/project_name_2.csproj : error NU

Basically, what I want to build is a project on .NET 6 ASP.NET MVC project, however, I tried to use well the following images without luck. The image I was setting is however, I got the following error:

rpc error: code = NotFound desc = failed to pull and unpack image "": failed to resolve reference "": not found
Let me know if you need anything else from me.
Kind Regards,
Caroline R Atlassian Team Mar 04, 2022

Hi, Victor. 

Thanks for getting back to us and sharing the additional information. Before we continue, I just would like to set the expectation that we are not proficient with how .Net technology works, but we will assist as best as possible from our side.

In order for us to verify if the issue is related to the Pipeline, you will need to debug the build locally and let us know the result. You can access the following link to check how to perform this test:

The error that you are getting while pulling the image is actually expected as the image you are specifying doesn’t exist. Could you please try to use to pull the image if you would like to use the .Net SDK 6.0 version as mentioned here?

Please let us know how it goes and don't hesitate to ask for any further information if needed. 

Kind regards, 

Hello @Caroline R ,

Thank you for your help! By updating the image to the one you shared on the comment, the build of my .NET 6 project worked very good.

Thank you so much for sharing the debugging details as well. I will definitely configure it locally for tests.


Caroline R Atlassian Team Mar 07, 2022

Hi, Victor! 

Thanks for getting back to us! I'm glad to know it worked :)

Kind regards, 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events