Thank you for your feedback! We have determined that this issue is not a bug. If the projects in question are not using packages.config but project json or package reference for specifying the nuget dependencies this is by design. If the project is using packages.config, on uninstall/update the packages would be cleaned out from the packages folder(since it is created on per solution basis).
However, in other cases, the packages are put under global packages folder, shared by different solutions and projects, hence these can't be deleted when they are removed from your particular project. This is by design. If you are seeing this behavior in packages.config case, it would be great if you could let us know more details of the project type and any other relevant information so that we can look into it. Dru 180a driver for mac.
Do let us know. I have experienced this as well. I just removed the Microsoft.VisualStudio.Web.BrowserLink package. It displayed the dialog to remove it, I said OK. I Cleaned and Built the project and it seemed fine. Then I looked at the NuGet page I see that the package is still listed. I click to Uninstall it again, receive the confirmation dialog, click OK, and then get the error Package with id 'Microsoft.VisualStudio.Web.BrowserLink' does not exist.0 If I close the solution and then re-open it, the package is no longer listed.
Visual Studio for Mac Announcement: This forum has been migrated to provide our customers one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Visual Studio Developer Community. Extension for Visual Studio - A collection of tools to automate the process of downloading, installing, upgrading, configuring, and removing packages from a VS Project.
I ran the project and it operated fine. I then went and removed another NuGet package. This time, it correctly removed it from the list. I then did some work in the solution and then added a new package via NuGet.
After accepting the install dialog and the license dialog, the Output showed it had been successfully added but it did not appear on the 'Installed' tab of the NuGet window. I then saved the solution, closed and re-opened it, and the package appeared on the 'Installed' tab. So, it seems that something is reset by reloading the solution that allows updating the NuGet package list. The 'Output' shows clearly that the package is installed/removed, it is just not updating the NuGet page displayed in the editor.
@Nikolche Kolev - not sure if I can answer your first question: Searching in 'Tools Options' for 'restore' it shows 'Package Restore' with 'Restore on Project Open' and 'Restore on Save' set true for both 'Bower' and 'NPM'. As to 'is it reproducible', I did the following:.
Added the Microsoft.VisualStudio.Web.BrowserLink package back to the project (API.NET Core WebAPI project). Closed the solution then closed VS2017. Opened VS2017 and opened the solution. Under 'Manage NuGet packages.' , I selected that package again and clicked to remove it.
I clicked OK in the dialog and it removed the package from the list. So, it wasn't reproducible this time. Of course, any number of other steps done previously could have set it up to cause this condition. Also, since posting this issue, I have received the update to VS2017 'Version 15.2 (26430.13) Release'. So that may have resolved this as well. I will monitor and will update in about a week with any results positive or negative.
8 January 2014 There is a fair amount of info on making and publishing NuGet packages but I couldn’t find a simplified guide for the simple case. Here it is and start by downloading and putting it in your path. Multi-platform considerations (optional) Supporting multiple platforms gives you a choice to make:.
One project with MSBuild magic. Multiple projects If you can go with PCL do it. For we use platform-specific system info and hooks so it’s not an option – we went with multiple projects.
Multiple projects Creating a separate.csproj for each platform and putting in the same folder means adding files isn’t too painful (show all files then include the ones you need) but you do need to take steps to make sure the build process for the projects don’t interfere with each other by separating the bin and obj paths:. Set the output path in the Build tab of project properties to be unique per configuration to for the bin files, e.g. “bin Net45 Release ”.
Edit the.csproj file adding a BaseIntermediateOutputPath tag for obj files, e.g. Create your.nuspec definition Now that you know which release dll files you need to include you can go ahead and create the nuspec file that tells nuget how to package your files up. Open a PowerShell and type nuget spec to create you an XML file to edit in your text editor Once you’ve entered your author details, a snappy description and links to your project page and license you can then add the files. Libraries will want to copy the.dlls into the lib folder with element like these. Each platform will require a specific target and they should use platform name (e.g. Net45, sl5, windows8) described in the. That page has a lot more detail on things such as content file types etc.
If you prefer a graphical UI then will make your life easier. Remember to check your.nuspec file to source control (there is nothing private in it) and add it to your solution as a solution item so it doesn’t get missed.
Create your.nupkg package The easiest part of the process. From PowerShell type.
Nuget pack yourfile.nuspec If all goes well it will create yourfile.nupkg. Test your package Just because your package was created doesn’t mean it works and you don’t want to publish to the world until you know it works especially given you can’t delete packages from NuGet:. Create a folder to be your own private testing NuGet repository, e.g. C: testnuget.
Publish to your test repository with nuget push yourfile.nupkg -source c: testnuget. Configure Visual Studio to use your test repository by going to Tools Library Package Manager Package Manager Settings Package Sources and then adding your test folder to the Available package sources test. Create a new test application and then add a reference using Manage NuGet Packages to choose your new package from your test repository. Write a few lines of code to test you can actually use your package OK!
Publish to the world Okay, you’re now ready to publish. If you haven’t yet you’ll need to do that first.
Top 20 Nuget Packages For Mac
Go to and copy your API key. Run the PowerShell command nuget setApiKey followed by your API key, e.g. Nuget setApiKey 99995594-38d2-42cd-a8b1-ddcd722bb7e7. Run nuget push yourfile.nupkg again this time without the -source option to publish to the default public repository )amien.