Visual Studio 2017 NugetPackageManager not syncing with private repository - nuget

I have a TeamCity hosted Nuget package repository. I see the package in the repo xml, http://teamcity.mycompany.com:8080/httpAuth/app/nuget/v1/FeedService.svc/Packages(Id='MyCompany.MyPackage',Version='1.0.21')
But when I look to reference the package in my visual studio project, it still says the previous version is the latest one. I attempt to click refresh, doesn't show the latest version. I confirmed the 1.0.21 is listed as absolute latest version by going directly to the package and checking the xml.
I have attempted to use the report a problem in the upper right of the IDE, but it's unresponsive. hopefully someone from Microsoft sees this.

Related

Why is the latest stable version of Newtonsoft showing in Nuget Package Manager as 12.0.3 in one project and as 9.0.1 in another?

In my class library, Manage Nuget Packages shows the latest stable version of Newtonsoft as 12.0.3. In another application that references the class library, Manage Nuget Packages shows the latest stable version of Newtonsoft as 9.0.1
What would explain that difference, and how is it fixed in Visual Studio 2019? When I try to compile the application, it fails with the error that the class library's version of Newtonsoft is newer.
EDIT: I think I've found the reason: in the top right corner of the window the package source for the application was not nuget.org but Visual Studio Offline Sources.
Why is the latest stable version of Newtonsoft showing in Nuget
Package Manager as 12.0.3 in one project and as 9.0.1 in another?
When you install a nuget package, you should select the right nuget package source.
As it shows that, Visual Studio Offline Sources is your local nuget caches. It is required that you download the corresponding nuget version and then exist in this data source. So it depends on you and not all versions of the package are fully displayed.
nuget.org is the ultimate destination for developers releasing nuget packages. You can find every version of the package here. So you should check this link.
Check and enable that link.
Then, open Nuget Package Manager UI and choose nuget.org and you can find it.

monogame.extended.entities no world in namespace`

VS 2017, monogame project, pulled in the MonoGame.Extended.Entities dependency. I went to the class browser and I don't see the world object. I can see it's apart of the code on github and should be there.
I installed the dependency through the nuget manager in vs 2017.
using version 1.1.0 MonoGame.Extended.Entities
I had this issue as well. The demos on their GitHub page all function normally, and they reference the source code, not the nuget packages, so the night versions are lacking . The 1.1.0 nuget version doesn't appear to match the GitHub version 1.1.0, which is a little unusual. I fixed it by updating the packages to the prerelease version. The method I used can be found in their docs:
http://docs.monogameextended.net/NuGet-Pre-Release/

nuget gallery versions and github

If I go to nuget gallery and search for a package e.g. Newtonsoft.Json
And I see a version available e.g. as of today 11.0.1-beta3 (current version)
I then go to github for the project. In this case:
https://github.com/JamesNK/Newtonsoft.Json
I look at releases and Tags and only see the "latest" which is 10.0.3
My question is where is 11.0.1-beta3 (current version)?
And how do I see what in it? e.g. I want to see if an issue has been fixed and is available
Release Differences
Newtonsoft.Json 10.0.3 is the latest / current Stable Release.
Newtonsoft.Json 11.0.1-beta3 is the latest / current Beta Release.
You can locate the Newtonsoft.Json 11.0.1-beta3 in the Nuget Gallery by scrolling down to the "Version History" section. Or just visit this link.
Source Code
Regarding taking a peek at the code, since it is indeed open-source software, you can view the release notes and download the source-code from the Github Release page, as you saw. But of course only release versions will be listed here -- beta versions, still being a work-in-progress, will not.
Other than just installing the 11.0.1-beta3 package and inspecting the Newtonsoft.Json files in your IDE, you may be able to step through the source code in the Nuget Package following this method. Not sure why you would, but if that's what you need go for it!
Screenshots

Visual Studio 2017: Package Restore failed, Rolling back Package changes for 'Projectname'

Added the new Package using Package Manager console or manage nuget packages in Project it's not added project it's Throw below Error.
I was Check some Links Not give proper reason. why this problem in coming in vs2017
Anyone Know Share the knowledge.
Thanks in Advance
Visual Studio 2017: Package Restore failed, Rolling back Package changes for 'Projectname'
You could not install the package exceldatareader.dataset to the UWP project. That because this package only have the .NET Framework assemblies, which is not compatible with UWP project. You can download that package from nuget.org, then open it, you will find this package only have the assemblies for .NET 2.0 and .NET 4.5:
So this package is not compatible with UWP project, you can find the error message in the output window when you install it to the UWP project:
Hope this helps.

Nuget not restoring packages in visual studio 2015

I installed the Visual Studio 2015 yesterday on my work machine and map a project from TFS that i was working on the previous version (VS 2013). All the projects in this solution are build on top of .NET framework 4.5.1 . When i try to make a Restore Nuget Packages it says that all the packages in the packages.config files are downloaded already, but im getting a lot of compilation errors. The Microsoft.Exchange.WebServices.Data; reference for example, its declared on the packages.config file but im getting the 'red' error on the using clause of this reference in visual studio.
ThereĀ“s other package that the nuget says it is installed but in the references its possible to see an yellow triangle. And this package is on the packages.config too.
Is that something different in this new versio of nuget?
Ps. I already installed the update of the nuget program.