Microsoft visual studio 2017 nuget browse not working

From Solution Explorer, right-click the PartsUnlimited.Shared project node and select Open Folder in File Explorer. On the opened window, select nuget.exe version v5.5.1

On the feed created before click Connect to Feed | NuGet.exe | Get the tools. In the next task weвЂ™ll use NuGet.exe to generate a NuGet package directly from the built project, but it requires the project to be built first. (Confirm the same if you are using VS2019) NET Framework 4.5.1 and click Yes to confirm the change. Right-click the project node and select Properties. (If VS2019 used, look for вЂњclassвЂќ in the finder and select Class Library (.NET Framework) and choose version 4.5.1) We will now create a shared assembly that will be published as a NuGet package so that other teams can integrate it and stay up to date without having to work directly with the project source.ДЇrom the Visual C# section, select the Class Library (.NET Framework) template and set the Name to вЂњPartsUnlimited.SharedвЂќ. Task 2: Creating and publishing a NuGet packageДЇrom the main menu of Visual Studio, select File | New | Project (вЂњCreate a new projectвЂќ in VS2019).

Visual Studio is now connected to the new feed.Д¬lose and Reopen the other Visual Studio instance used for cloning the PartsUnlimited repository ( prerequisites Task 2), so that it shows this new source. Set the Name to вЂњPartsUnlimitedSharedвЂќ and paste the Source URL copied earlier. Locate the Package Sources section and click the Add button to add a new package source. Select Tools | NuGet Package Manager | Package Manager Settings. Do not use the instance open from cloning the primary Parts Unlimited solution. This is the only thing Visual Studio and NuGet need to start taking advantage of the new feed. In the Connect to feed window, select Visual Studio and copy the Source url. Leave the default options.ДЄny user who wants to connect to this NuGet feed must configure their environment. Set the name to вЂњPartsUnlimitedSharedвЂќ and click Create. Select the scope as Organization for this lab. This feed will include common functionality that can be shared across projects in this organization. The scenario in this lab will focus on the workflow for using Azure Artifacts, so the actual architectural and development decisions are purely illustrative. This feed will be a collection of NuGet packages available to users within the organization and will sit alongside the public NuGet feed as a peer. Task 1: Creating and connecting to a feedД¬lick Create feed. It comes pre-installed in Azure DevOps Services, Azure DevOps Server 2019, Team Foundation Server (TFS) 20. This lab requires you to complete tasks 1 and 2 from the prerequisite instructionsДЄzure Artifacts is an extension to Azure DevOps Services and Azure DevOps Server. Want additional learning? Check out the Manage build dependencies with Azure Artifacts module on Microsoft Learn.

Microsoft visual studio 2017 nuget browse not working