Through the devDept NuGet Server https://nuget.devdept.com/nuget users can easily include the Eyeshot packages and update to the latest official version.
The following steps will demonstrate how this can be done in Visual Studio:
1. Navigate to the Package Manager Settings menu.
2. Add a new source in the Package Sources section
3. In the Source field fill the address of the devDept NuGet Server and click Update.
4. The devDept Server is added and ready to use. Click on the Manage NuGet Packages menu.
5. Set the devDept Server as a package source. Enter user credentials (email and password from your devDept account) when prompted and search for the needed package.
Resetting the devDept NuGet Credentials
If you want to reset the cached credentials from Visual Studio, follow these steps:
1. Delete the Package Source.
2. From "Control Panel" > "User Accounts" > "Credential Manager" > "Windows Credentials," delete the two entries related to devDept.
If that's not enough, make sure to close all instances of Visual Studio and also delete the v3-cache folder located in %AppData%..\Local\NuGet.
Comments
Hi,
first of all, thanks for adding this! It is a great quality of life improvement to have NuGet packages and even a NuGet feed available.
Following your discussion with Gert van de Venis in your other related article I would like to understand what's the best practice to restore those NuGet packages in our CI pipeline build processes.
As I understand, I currently need to provide my DevDept login credentials to the CI pipeline runners so they can actually use the NuGet feed.
Is this the intended way or are there any alternatives to this (e.g. generating an access token from my account and using that instead)?
Kind regards,
Michael
Hi Michael,
If you are only using the stable versions of the packages, it should be enough to provide the credentials in your production pipeline’s NuGet server settings.
However, if you also need to use nightly builds, I recommend configuring a local folder where you can copy all the required packages, as explained in this article.
If you need further support for your specific case, please feel free to open a support ticket.
Please sign in to leave a comment.