question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

UI: Add setup page describing how to add the repository to nuget config(s)

See original GitHub issue

Do you want to request a feature or report a bug?

Feature

What did you expect to see?

  • A link or page describing how to add the Package Repository to a Nuget.config
    • Either the users config file
    • Or a project-specific Nuget.config file.
  • The page should include the actual url, and in case of Private Feeds (#36), a key (if possible) in the feed url

I imagine that next to the BaGet title, an “info” or “setup” link could be added.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
LordMikecommented, Dec 18, 2018

Looks great. Awesome with this new UI. I take it Routing made its way in now, so we can start using paths - ie. show different versions of packages 😄 ?

Notes:

  • The push command includes newtonsoft in 2 out of 3 cases, Paket is the odd one out
    • I’d use package.nupkg instead of newtonsoft. (less characters to remove after pasting, while still keeping it concise)
  • The link to docs should be target="_blank"
1reaction
LordMikecommented, Dec 1, 2018

You should absolutely add a link to documentation, from the running instances.

But. I’d still add a custom page that includes my url. You could show how to:

  • Add my url to feeds (“Add <url> to the Nuget package repositories in VS”)
  • Push a package to my url (“nuget push SamplePackage.1.0.0.nupkg <your access token> -Source <my url>”)
  • Add symbols url to VS with my url

This would make the adoption easier for new developers who can just be pointed at BaGet and get up to date information on what to do. They don’t have to do any url replacements to replace “localhost” in the documentation with some custom domain. It’d make it self-explaining 😃.

Read more comments on GitHub >

github_iconTop Results From Across the Web

nuget.config File Reference
Add a nuget.config file in the root of your project repository. This is considered a best practice as it promotes repeatability and ensures ......
Read more >
Setting NuGet Package Source - Telerik UI for WPF
Go to the UI for WPF Downloads page. · Download the . · Navigate to the "Package Manager Settings" menu. · Add a...
Read more >
NuGet Repositories
For Linux installation: The file is located under ~/.config/NuGet/NuGet.Config · For a Windows installation: Locate the file usually under %appdata%\NuGet\NuGet.
Read more >
NuGet packages in the Package Registry
To install a NuGet package from the Package Registry, you must first add a project-level or group-level endpoint. Install a package with the...
Read more >
What is NuGet (How it Works for Developers Tutorial)
In Visual Studio, click on Tools from the Top Menu Bar and select NuGet Package Manager => Package Manager console. The Package Manager...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found