Skip to content

Instantly share code, notes, and snippets.

@vcolavin
Last active May 23, 2017 01:02
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save vcolavin/d94bf9dacf2c6b041c129ee57a3b0f50 to your computer and use it in GitHub Desktop.
Save vcolavin/d94bf9dacf2c6b041c129ee57a3b0f50 to your computer and use it in GitHub Desktop.

To anyone working on .Net environments, if you encounter build errors referencing FV.Logger and not being able to find version 1.0.0.0, you may need to set up your NuGet to find our in house repo. To do so from VS

  • go to Tools>NuGet Package Manager> Manage NuGet Packages for Solution.
  • In the upper right area of the dialog that opens will be the words 'Package source:' followed by a drop down and a gear icon.
  • Expand the dropdown and look for 'CommonSource'. If it exists, you don't need to do anything.
  • If it does not, click the gear icon to open the Options panel.
  • From here click the green plus sign ( + ) in the upper right to add a generic package source to the list.
  • Next move the cursor to the Source: text box, which currently displays http://packagesource.
  • Set URL to \\usjenkins01\Jenkins\CommonSource and set name to CommonSource, then click Update, followed by OK to close the Options menu.
  • Finally, if an option to Restore Packages is currently visible from the NuGet menu, click it, otherwise attempt to Rebuild your solution from the Build menu and watch for Restore Packages to appear, or for NuGet to do so automatically.
  • If the problem persists, delete the Packages folder from your repo and return to the NuGet menu to attempt to manually Restore Packages again.

You've also gotta be logged in to Jenkins: http://usjenkins01:8080/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment