I am wondering there is no benefit of uploading package on nuget then why people spent too much time to create a package and upload it on nuget?
Yes, We can distributes packages without using nuget.
But think:
How will you manage versions?
How will you Define dependencies for the packages?
Where you will explain technical specifications and documentation of package?
How will you know if your package is useful or not?
How will you know that how many times users has downloaded your package?
How will ensure to your user that your package is valid and went through security checksum?
If you have all the answers then there is no need of uploading packages on nuget.
Thanks
Related
We have a web app project that still uses NuGet for content packages management (jQuery, Knockback, knockoutjs, etc.). We are trying to convert to use LibMan, and running into an issue where some older packages do not exist (for instance walltime-js). How do we work around this issue?
Try using a different provider. The current default, Cdnjs, is a curated catalog; the other two providers, JSDelivr and Unpkg, host any package that's available in NPM and thus have much broader catalogs.
Using LINQPad I've added a private feed to Visual Studio Team Services. However one of my packages requires a pre-release package: Quartz.Net in my case. I've ticked Include Prerelease but I think it's getting confused and trying to load the package from my private feed rather than NuGet.
I've tried to work around the issue by loading the package into the local package cache. LINQPad doesn't seem to consider this. Other than uploading these packages into my own private feed, what options do I have? I'm not going to alter my own packages to get around LINQPad's shortcomings.
Note: I've setup the VSTS feed according this question.
Here is what my NuGet feeds look like in LINQPad
Changing the package to pre-release fixes this issue, and add the pre-release packages dependencies to my own feed.
Now LINQPad attempts to add the package. Mind you I now get another error;
"There are no usable .NET assemblies in package
'MyPackage.Common(Prerelease)'
That's down to NET Standard & NET47 support.
I have set up a small test Nuget private repository on my machine following this guide.
Everything is working perfectly and I can publish packages, update versions, download them etc. The only problem is that the DownloadCount of my packages is always 0 regardless of how many times I download it.
I downloaded NuGet source but could not find a place where this value is updated. Moreover, nuget does not seem to use any DB technology so probably the feed is just generated on demand from the contents of the Packages folder.
Does anyone have any idea if this is a known issue or if it's a problem in my setup or if I should just add some code to the server to record downloads myself?
Thanks!
NuGet.Server based web sites are simply a front-end exposing an OData feed on top of a file share. There's no real database behind it, no indexing, no auditing, tracing, metrics or statistics, or any of that kind of stuff.
You could build it yourself, or take a look at alternatives such as MyGet, ProGet, Artifactory, etc.
Having (presumably) understood the motivation behind Nuget, I want to know, whether we still require internet access to download a package which is already being downloaded earlier for different project in different solution?
I believe you can even set up your own feed stored on the file system as described here.
You can setup your own local NuGet repository as As Denis Ivin has already said.
NuGet also has its own local machine cache which keeps NuGet packages that you have installed previously (C:\Users[UserName]\AppData\Local\NuGet\Cache). You can install these by selecting the Recent packages tab in the Manage Packages dialog.
Having your own local NuGet repository is probably better since the cache could be cleared.
I have an open source project SystemWrapper. Someone recently asked me to add it to NuGet gallery. I had no problem to create a NuGet package. However, I cannot figure out how to add my package to NuGet Gallery.
Can someone point me to a link that describes how I can do that or tell me the steps I need to make.
I think the page at http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package may be what you're looking for.
The basic process appears to be to register for an account at NuGet.org, tell your local NuGet package manager your API key, then "push" your component.
Good luck!