I think I have 2 options:
1) Download from CodePlex: http://valueinjecter.codeplex.com/
2) Download from NuGet official package source (currently download count is only 133).
I prefer to download from NuGet, but I'm a little worried about its safety. I have no idea who made the package. Is the package on NuGet made by ValueInjecter's author, or some other trusted user?
Thanks
use the codeplex site for now,
the package on nuget is made by the author, but it's not the latest version (sorry)
Related
I'm building a Blazor component and want to automate the build process. Currently the package builds properly and is pushed to nuget.org with its proper license and icon files but I can't find anywhere how to include docs. I have to manually sign in to nuget.org and update the docs to point to the same github readme link.
Is there any way to automate this process?
The feature is only for nuget.org website and is not a part of nuget cli now. And you are not the only one who wants to reflect this problem.
There is a similar github link.
After feedback from many users, the Team is working hard to add this feature to nuget cli. You can follow this link to keep track of the progress.
All the data for your package should be included inside the library project (Properties). Once you build the library and upload to Nuget, the links, descriptions and everything else will be displayed when someone searched for your package and previews on visual studio or on Nuget.
Take a look here, you will see where to find everything: https://youtu.be/FTnua-kh-bY
Does NuGet support global package installation like NPM and Composer? If so, how do I do that? Also, how do I reference globally installed packages in my Visual Studio projects?
So learning from #Lance's tips, I went ahead and checked %userprofile%\.nuget\packages folder, and indeed it contains all the packages that I have downloaded in the past. Unfortunately though, Visual Studio (I'm using Community 2019) does not allow you to install any of these packages into a new project. The Browse page in NuGet Package Manager UI displays online results only from nuget.org.
But then I found another clue. In Visual Studio Tools > Options > NuGet Package Manager > Package Sources, you can add custom sources. So I went ahead and added my cache folder as an alternate source.
Note that there is a separate "Machine-wide package sources" entry too that cannot be modified. I checked that folder and it contains mostly Microsoft's own packages (one exception that I found there was NewtonSoft.json). I have no idea how this folder is different from the nuget cache folder and how I can download a package to this folder.
So far so good. The Package Manager now shows all previously downloaded packages from cache when I select this source from the drop down (sources dropdown is in top-right corner). I can then select a package and install it from local source instead of downloading it from the Internet.
Hope this helps someone down the line.
Nuget.org is now able to allow for authors of a Nuget package to sign their packages so that users of the package can verify that the package has not been tampered with and it builds in some authentication of the author of who made the package. Here is the blog announcing this.
It sounds like anything new will require the package to be signed but the past packages will not be signed. Is this correct? How can I know that a package has been signed?
I am using Visual Studio 2017 above the version 15.8.5 and Nuget Package Manager 4.6.0
No, there is no requirement for packages to be author signed to upload to nuget.org. There are some more docs on signed packages, including the reference page and signing packages.
NuGet.org will also sign packages. Most popular packages are already repository signed at the time I'm writing this, and all other packages will eventually be repo signed. Yes, there's a difference between author signature and repo signature, so some packages will have two signatures.
To check if a packaged is signed or not, you can follow these instructions. Or open the package in NuGet Package Explorer, although you need to know what to look for, as I'm not sure there's anything that explicitly says unsigned. Or you can open the nupkg with any program that knows zips (or if it's a package you've already restored, go to the folder in your global packages folder %USERPROFILE%\.nuget\packages and look for a file named .signature.p7s.
I need to update a package Package01, which lives in a private source, for multiple projects in a solution from version 1.0.1 to newest version 1.1.0. If doing this update from Package Manager UI, this step needs to be repeated many times.
Is it possible to do just in one step? Thanks for any suggestion.
You can update a package for all projects in a solution from the Package Manager UI or from the Package Manager Console.
Using the Manage Packages dialog right click the solution and select Manage Packages for the solution. Then update the package. You will be able to update it for multiple projects in one step.
You can also do a similar thing from the Package Manager Console. The command below will update jquery to the latest version for all projects in the solution.
Update-Package jquery
There is more documentation on the Update-Command on the NuGet web site.
I have various Nuget packages installed to my solution. Some in my domain project and some in my MVC Front End project.
This all works quite happily. However if you get the project new from source control I can see I have all the packages in the packages folder. However they all appear to have an exclamation after them in References for the projects.
If I use nuget command nuget install .\ProjectFolder\Packages.config it seems to install the pacakges again but the refrences still don't appear. I have to manually install them using nuget manage references and install them individually. Which is a bit of a hassle for new developers starting projects.
Seems a bit odd? Is something wrong or is this normal? Shouldn't Nuget/VS2010 know that all packages exist and be happy as the packages are all in the local file system from source control (I know there is a debate about keeping them there but lets leave that aside)
Thanks
Graeme
Updated June 28, 2014
You might consider a reinstall of your packages. See this thread: How do I get NuGet to install/update all the packages in the packages.config?
Leaving the outdated answer below for history, but note that the MSBuild-based package restore is currently considered a bad practice (more info: http://www.xavierdecoster.com/migrate-away-from-msbuild-based-nuget-package-restore)
Outdated answer below:
Not a direct answer to your question, but maybe a valuable suggestion when using NuGet with TFS.
You might consider the no-commit strategy for NuGet packages, and use the NuGetPowerTools Enable-PackageRestore command.
More info here:
http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages
http://blog.davidebbo.com/2011/03/using-nuget-without-committing-packages.html
http://blog.davidebbo.com/2011/08/easy-way-to-set-up-nuget-to-restore.html
http://www.xavierdecoster.com/post/2011/07/18/Continuous-Package-Integration-NuGet-vs-Source-Control.aspx
http://www.xavierdecoster.com/post/2011/10/17/tell-tfs-not-to-add-nuget-packages-to-source-control-aspx
Install NuGetPowerTools package and then Enable-PackageRestore from the Package Manager Console. That should fix it.
This is the short version of #Xavier response :).
I'm guessing it isn't normal. I removed the entire packages folder. Re-added all packages to my solution and then committed all the changes.
It now it seems to work if I re-get the site from source control. Maybe something was corrupted. The project was originally started before I was using source control and nuget. Maybe some sort of initial setup issue.
Thanks
Graeme