I have a network share that I dropped a nuget package I created into. I configured Nuget in VS2010 to add the share as a package source. However when I select it, it shows no packages.
If I have the package in a local folder, it works fine.
Any clues?
Easy enough to test. Open Windows Explorer using the same credential you use with VS2010 and point to the nuget share. If you can see packages there, then you should see them in VS2010 also. If you can't see the files in Windows Explorer - then check the permissions as #PHeiberg suggests and make sure you have list and read. Since groups are probably in use, search for your login from effective permissions as in this screenshot:
Related
I have created nuget package (.nupkg) and hosted that package directly on one of http servers
http://someserver/location/sub-location/nuget/MyPackage.1.0.0.nupkg
So if i just copy paste this URL in browser, packages gets downloaded immediately.
But, I want to download this package as part of nuget restore command.
I have used section in nuget.config file to download package from Folders, nuget.org, artifactory etc. But this particular case not working.
I don't want to run additional command to download package (for example, i don't want to use Curl )
I want some configuration done so that i can download this package in same way as other packages from other nuget repositories .
I don't want to run nuget server for hosting.
Thanks,
Atul
Sleet is a static NuGet feed generator. Using it, you can generate files and use any web server to serve static files.
However, since this includes a static response to search queries, if anyone uses this feed with Visual Studio's Package Manager UI, it doesn't matter what search terms they type, they'll always get the same search results. When VS searches a package source, it requests a maximum of 25 results, but since Sleet is static, it returns the entire list of every package in the feed. Before Visual Studio 2019 16.7, NuGet would show all the search results and if the Sleet feed contained enough packages, it would crash VS with an out of memory exception. VS was changed to only take the first 25 results and ignore the rest, so it will no longer crash. But this means that it's impossible now in PM UI to see more than the first 25 packages. If search results are not important to you, the Sleet sounds like a good fit.
I have build a nuget package at published it to a nuget.server site. But when I try to use the package form the server the .targets file from build folder is not in the file. But if I use the package from a local folder it works as it should. How do I get it to work ?
If i look in the package in the folder on the server it looks ok.
It's not clear to me if you mean using (referencing and restoring) a package, or building (packing) a package.
If the problem is with packing the nupkg, NuGet requires the props and targets files to have specific filenames in specific folders, but if you got it to work at least once, you probably already know that. If this is not the problem with packing, you need to give us more information because not using the correct filename convention is the most common problem and I can't guess what else the problem could be. In particular, if the package is being packed differently on your local machine compared to when it is packed on the server, it means there is something different between how you pack on the two computers, so we need more information about how the build and pack work with your project.
If the problem is with using (restoring) the package, there are a few possibilities. My best guess is that you once had a package without the targets file working correctly, and you restored the package on the server. By design, NuGet packages are immutable which means it's invalid for the contents of a package (same ID and version) to change. This allows NuGet to download the package from a remote feed once, save it in the global package folder (not a cache; they never expire) and the next time NuGet needs to restore the same package (id + version) it uses the one in the global package folder, it does not download again. This means if you once built a bad nupkg and restored it on a machine, then fix the nupkg and kept the same version number, that machine will never get the fixed nupkg. You need to delete it from the global packages folder. I'm not 100% sure, but I think if you have a local file feed and you restore a project that uses packages.config, the nupkg does not get saved in the global packages folder, so doesn't have the same problem. In short, I think the problem is that you changed the nupkg contents once without changing the version number, and one of the machines has the old copy in its global packages folder that it keeps using.
If that's not the problem, the next most likely cause is that the nupkg on the server feed has different contents to the nupkg in the local feed. I've never used NuGet.Server, but some nuget respositories (like nuget.org) do not allow overwriting nupkgs. So, if you pushed a nupkg to your server, fixed a problem in your nupkg without changing the version, then tried to push again, the second push might have failed.
In summary, your question doesn't provide enough information for us to help you, but I wrote about the most common issues above. If it doesn't help, you need to provide us with more information. An example of the problem is the best way to give us enough information to help you.
I've been trying to install Enterprise Library 6, and it's been a pain. I tried following Enterprise Library 6: Installation and VS2012 Configuration, but I'm having issues with the powershell command. I also tried opening install-packages.ps1 and pasting in powershell, and I keep continue errors. I'm not sure if it's my machine and the restrictions it has, but I don't want to go through this installation process just for one call to a stored procedure.
I rarely use powershell, and I don't want to start learning it today. Is there a way to just download the dlls needed and add them as reference to my project?
I had already added Microsoft.Practices.EnterpriseLibrary.Data as reference, and the project builds well, but when it runs, I get an error with one of the methods. It seems that there are other dlls I need to add (Microsoft.Practices.EnterpriseLibrary.Common), among others.
I just want to download these dlls and add them as reference. I don't want to go through any installation process.
Is this possible? Thanks.
I downloaded Microsoft.Practices.EnterpriseLibrary.ConfigConsoleV6.vsix. Then I opened in winrar, copy/pasted Microsoft.Practices.EnterpriseLibrary.Common.dll to my bin folder, and added as reference to my project.
Then I downloaded enterpriselibrary.data.6.0.1304.nupkg from nuget.org and opened it with winrar. Then I copy/pasted Microsoft.Practices.EnterpriseLibrary.Data.dll to my bin folder, and added as reference to my project.
I have found a dll that is provided via Google Code and I couldn't find it in NuGet. I want this package to be available via a NuGet install, because I want to reuse it in several packages and NuGet seems like the perfect way to do this.
https://code.google.com/p/protobuf-remote/downloads/list
Is it possible for me to generate a nupkg out of these dll's and publish it to NuGet.org? What are the legal limitations to this action?
There are a number of other users that have run into this issue. It seems like the common solution is to create an "Unofficial" package and reference that for the time being (until Google publishes their library as a NuGet). Just make sure to very clearly label the package as unofficial. See these examples.
As for the legal ramifications...
Please look through protobuf-remote license and review the distribution and derived works details. Currently the license is GNU Lesser GPL. Sorry, but you'll have to make your own call on if publishing the NuGet package would be permitted under this license. ;)
I would recommend you instead create a local NuGet package source by pointing to a file share. This can be local on your computer or on a network file share.
Also, if you don't want to update every workstation, you can update the NuGet.config file in your project to point to this source and commit that config file in your source control repository for all users to get automatically. Just note that any change to a NuGet.config file requires you to restart Visual Studio.
And FYI, take a look at how you can chain multiple NuGet.config files.
So here is the situation. I want to bundle Google Chrome Portable by itself. The only modification I would make is to change the default homepage, and add a shortcut link to the desktop. I also can't use the included Google Chrome installer because I would need to change the default homepage.
What should I use to make a simple installer that just unzip the Google Chrome folder into programs and create the shortcut on desktop? I don't need anything fancy like program registration or anything like that, in fact, most of my clients probably will not have installation rights on there computer.
Now my project is in Visual Studio 2008, but I am willing to use any other type of packager.
You can also try the free version of Advanced Installer, i.e. by creating a "Simple" project. There is also a five-minutes tutorial on how to create the package
I went with the WinRar SFX Archive File, with auto-run after it finishes.