Thanks for the guide. One question though, can other people outside of my organization see my package? I ask because when browsing my feed I am able to see other people's packages even though I am pointing the package source to the generated link provided by azure.
Hi Bharath Simha, I have not personally worked with salesforce development but it appears your first step would be to start digging around in their documentation here: developer.salesforce.com/docs
Thanks for the video, Developers need to use these packages to install locally, how can i give access without providing contirbutor access tothe Developers in Azure Artifacts. actually they were not able to install the packages
Thats a great question! A coworker of mine recently showed me this. You give them the package files that they package up from their project using the command line (or building with the checkbox set in dotnet core/dotnet6/etc). Then, users should put packages they were manually shared in a folder, and go to package sources in visual studio (tools->options->Nuget Package Manager->package sources), and add a folder on their harddrive as the source instead of a web address. Then, they can select the package in the package manager for solution or project, just like if it was a hosted one!
@@DataVids Thanks for the Reply... and when i directly gave them from VIsual studio... they are getting 401 errror. So what i found is Artifact credential Provider, with the help of that the Developers can use the Packages without any problm( correct me if i am wrong). But actually i am not able to Implement :)
This is a great question since a lot of us work on code libraries where as soon as we commit to a prod or dev branch in GIT we are then ready for the package to be used by our teammates. Microsoft now has a great article on this, and the copy/pastable pipeline part you want looks like it might be right at the top! Check it out: learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/nuget?view=azure-devops&tabs=yaml *************************************************** - task: NuGetCommand@2 inputs: command: pack packagesToPack: '**/*.csproj' packDestination: '$(Build.ArtifactStagingDirectory)' ***************************************************
@@DataVids Yes, use the simpler (but not trivial) way, using Pipelines, Feeds and Yaml. This video left me screaming "whhhhyyyy this is 2023+ not 2001 - a VS/Nuget Rabit-hole....."
Thanks for the guide. One question though, can other people outside of my organization see my package? I ask because when browsing my feed I am able to see other people's packages even though I am pointing the package source to the generated link provided by azure.
Nvm, I figured it out - I had nuget's public registry as an upstream source :)
glad you figured it out! There should always be an option to make it public or private to the organization.
Your awesome, thanks for this content
Nyc video thank U. I need to need universal package in azure devops to use salesforce environment can you explain me the steps..
Hi Bharath Simha, I have not personally worked with salesforce development but it appears your first step would be to start digging around in their documentation here: developer.salesforce.com/docs
Thanks for the video, Developers need to use these packages to install locally, how can i give access without providing contirbutor access tothe Developers in Azure Artifacts. actually they were not able to install the packages
Thats a great question! A coworker of mine recently showed me this. You give them the package files that they package up from their project using the command line (or building with the checkbox set in dotnet core/dotnet6/etc). Then, users should put packages they were manually shared in a folder, and go to package sources in visual studio (tools->options->Nuget Package Manager->package sources), and add a folder on their harddrive as the source instead of a web address. Then, they can select the package in the package manager for solution or project, just like if it was a hosted one!
@@DataVids Thanks for the Reply... and when i directly gave them from VIsual studio... they are getting 401 errror. So what i found is Artifact credential Provider, with the help of that the Developers can use the Packages without any problm( correct me if i am wrong).
But actually i am not able to Implement :)
How can we perform this in pipeline directly
This is a great question since a lot of us work on code libraries where as soon as we commit to a prod or dev branch in GIT we are then ready for the package to be used by our teammates. Microsoft now has a great article on this, and the copy/pastable pipeline part you want looks like it might be right at the top! Check it out: learn.microsoft.com/en-us/azure/devops/pipelines/artifacts/nuget?view=azure-devops&tabs=yaml
***************************************************
- task: NuGetCommand@2
inputs:
command: pack
packagesToPack: '**/*.csproj'
packDestination: '$(Build.ArtifactStagingDirectory)'
***************************************************
@@DataVids Yes, use the simpler (but not trivial) way, using Pipelines, Feeds and Yaml. This video left me screaming "whhhhyyyy this is 2023+ not 2001 - a VS/Nuget Rabit-hole....."
I like to upload my code into your repository. 😘 Get at me.😁🤣😁
Lol good one. That code better be protected, don't want a computer virus.