Configuring nuget azure artifacts source in MacOS
Greetings.
In my company, we are using Azure Artifacts in an Azure Devops Server 2019 on premise instance as an internal package source, and we are trying to work in a .net core project in a MacOS device. We are struggling to configure the internal source here, since in Windows is very easy and takes authentication and authorization from the Active Directory user logged in, but in Mac and Linux, this is obviously not possible.
We followed the instructions of the Azure Artifacts Credentials helper but this doesn’t seems to work, even setting the VSS_NUGET_EXTERNAL_FEEDS variable, that usually solves the problem in linux, but in Mac it doesn’t work. We also tried to authenticate using a PAT as ClearTextPassword.
Is there any solution for MacOS? Maybe something we’re missing out like login in the AD in MacOS credentials provider if that is possible.
I’ve read of using Visual Studio for Mac but it’s no longer an option since it’s being discontinued in august 2024, so we are using vscode and dotnet cli from now on.
Regards.
Greetings.In my company, we are using Azure Artifacts in an Azure Devops Server 2019 on premise instance as an internal package source, and we are trying to work in a .net core project in a MacOS device. We are struggling to configure the internal source here, since in Windows is very easy and takes authentication and authorization from the Active Directory user logged in, but in Mac and Linux, this is obviously not possible.We followed the instructions of the Azure Artifacts Credentials helper but this doesn’t seems to work, even setting the VSS_NUGET_EXTERNAL_FEEDS variable, that usually solves the problem in linux, but in Mac it doesn’t work. We also tried to authenticate using a PAT as ClearTextPassword.Is there any solution for MacOS? Maybe something we’re missing out like login in the AD in MacOS credentials provider if that is possible.I’ve read of using Visual Studio for Mac but it’s no longer an option since it’s being discontinued in august 2024, so we are using vscode and dotnet cli from now on.Regards. Read More