Develop Reference

Message - Update Functions Version on Azure

I have upgraded some of my Azure Functions to .netstandard 2.0, that is still in beta. Whenever I publish my Functions directly from Visual Studio, I get the following message:
The csproj file containing my Functions is already is targeting .netstandard 2.0.
Here is the setting in the Function App:
How can I "upgrade" the version of my local Functions?

I have done some tests on my side and reproduce the message you got. Just like #Connor has said, for function in beta version, the csproj file should include AzureFunctionsVersion as the illustration shows.
Once the AzureFunctionsVersion parameter is lost, the function will be recognized as using runtime ~1 despite the TargetFramework. So when the project is published to a beta function app in portal, it will remind us of the version change.

I ran into the same problem today during the creation of an Azure Function project in Visual Studio 2019. It needed a lot of sorting out but below turned out to be the solution for me:
In Azure:
Azure > Function App > Create
Then go to the settings and choose the runtime version, which is ~2 by default (meaning a 2.x version with auto updates enabled).
In Visual Studio:
VS Create project type C# > Cloud > 'Azure Functions'. In the second screen don't forget to choose for "Azure Functions v2 (.NET Core)".
Via the nuget package manager update the Microsoft.NET.Sdk.Functions package.
Also install: Microsoft.Azure.WebJobs (v3.0.9)
Also install: Microsoft.Azure.WebJobs.Extensions.Http (3.0.2)
Clean + Rebuild the project. Now you should be able to Publish directly from Visual Studio to the Cloud. Right-click on the project and choose 'Publish'. Then you should see an option to Publish to an Function in Azure cloud.
If not then the most likely reason is because you have a problem with your references / nuget packages / Microsoft SDK. Or the versions of those.

Package requires NuGet client version ... or above

After I download my project from GitHub and try to compile it I am running into the issue of "package requires NuGet client version ... or above" but I am using Visual Studio 2017 with the latest NuGet version for that version. The issue is fixed after building the package twice but is there a way that I could stop this from happening in the first place and have it so that these issues go away after the first compilation of the code?

I had a similar problem while adding NUnit via Nugget Manager. Instead of adding the package via Nuget Manager, I downloaded the framework's dll files from their website and add them as a reference to the project.
If you still want to use the NuGet manager, you have to upgrade to a newer version of Visual Studio

NuGet fails to find existing package

How it's possible that NuGet's Install-Package fails with Unable to find version 'x' of package 'y' when that exact version is released as NuGet to the official repository and it shown on the https://www.nuget.org/packages/y page.
Here is specific sample with nuget.org content and NuGet Install-Package command output.
UPDATE. Package sources are set to defaults (from nuget.org). Actually, you can see the issue just by running Install-Package Log4Net.Async -Version 1.3.0.
UPDATE 2. I want to highlight that it's not about some developer's machine - the same things happen on Visual Studio Online Hosted Build Controller.
UPDATE 3. Here is how NuGet tries to load package and it looks like NuGet API just broken, because all these requests fail with the error below.
Resource not found for the segment 'Packages'
Also NuGet produces a strange output on NuGet API calls that issued at VS search packages stage, please see here: http://pastebin.com/qveadrZB.

NuGet currently has some service issues related to search and package restore functionality. It is possible this is the cause of your package restore failure.
If other dev machines are working OK, it's likely they have access to a cached version of this package.

Clear your NuGet cache under options -> NuGet Package Manager

I know this thread is very old, but someone who has this problem like me in these days, find my solution for solving such problem here.
I've installed Visual Studio 2012/2015/2017 parallel, and 2012 failed with "package not found error".
So I take a look in the NuGet-settings in VS2017 and found the following package resource:
https://api.nuget.org/v3/index.json
I just added this location to the package resources and vòila, the searched packages where found and installed (in my example the HtmlRenderer).
But be careful with compatibility to Framework 2.0! This setting breaks maybe the functionality to version 2.0!!
Hope this helps someone sometimes somewhere.
Greetings

I'm a latecomer to this thread... I'm in Visual Studio 2017 - 15.9.4
I got this error today trying to pull from my private DevOps NuGet feed
CONTEXT:
the first time I called Install-Package everything worked, but, my NuGet was not assembled right, so, I re-published the NuGet pkg, and
when I tried to update my project that was consuming the pkg, that's
when I got the failure)
Switching my Package Source to "all" alleviated the problem.

After 4 hours struggle I found solution here
https://www.grapecity.com/componentone/docs/uwp/online-getting-started/config-nugetpackage.html
Tools > Options > NuGet Package Manager > Package Sources. > Click add button and add following one by one
nuget.org
https://www.nuget.org/api/v2/
GrapeCity
http://nuget.grapecity.com/nuget
NuGet settings in Visual Studio

Right click on references in your project
Manage NuGet Packages => All
Uninstall affected packages
If this does not resolve the issue, try to remove it from the NuGet config file located at
C:\Users\UserName\AppData\Roaming\NuGet\NuGet.config

Nuget version not correct?

I have a project that i cannot compile. When i try to do so I get the following error:
The 'Microsoft.Bcl.Build 1.0.14' package requires NuGet client version '2.8.1' or above, but the current NuGet version is '2.7.41115.310'.
Normally this would be simple. After searching I found this guide:
http://www.daimto.com/package-requires-nuget-client-version-x/
That explains how I can upgrade my Nuget client version. However, when i follow those steps, I find that I am already using the latest version of Nuget: 2.8.5
For some reason however, Visual Studio 2013 Ultimate is using an older version, and I don't understand why.
My install of Visual Studio Ultimate 2013 is a fresh install, after unninstalling Visual Studio for Web Express 2012. The previous version was giving me a considerable amount of problems and so I deleted it and moved on to 2013. I wonder if some cofig files were passed through, but I cant be sure.
How can I fix this problem?

From Tools → Extensions and Updates → Installed, uninstall “NuGet Package Manager” and install it again.

So, after searching around I found no answers, so I decided to look into the project folders. It happens that I have the main version of NuGet.exe, 2.8.5 in main folder, but the project was nowhere near that main folder.
This way, when I downloaded the project it simply used the NuGet version pulled from TFS (or so I assume), and that was the problem - that verison was Nuget.exe 2.7.4.
After replacing the "Nuget.exe" files (found in /.nuget folder of the project) the project finally compiled and everythign started working again.

You can also try update Nuget Package Manager directly from Tools > Extensions and Updates

In my case, a pending update of Visual Studio fixed the nuget version.
The update was the "Update 5" for VisualStudio 2013.
The update was listed under the menu Tools → Extensions and Updates, on the tab Updates.

I was getting this error from a recently cloned branch, but (in contrast to the above solution) found that my Nuget version in the project directory was the same as that in my solution directory.
I solved this by right clicking on the solution and Managing Nuget Packages for the solution. The Nuget dialog that popped up said that packages were missing and asked me to restore them. Once downloaded, the project built successfully.

I had the same issue when trying to install System.Net.Http and it said the nuget version needed to be version 3.0 or above. I tried few things but in the end, used Tools and Manage Nuget Packages and did a search and tried to install it from there when it said exactly the same thing - wrong version of nuget, but it popped up with an upgrade Nuget button too!
Hope this helps someone

Simply reinstall nuget in visual studio

Using Exchange EWS... Can't figure out how to access the dll?

I've downloaded and installed from here...
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=13480
As suggested here..
Getting started with Exchange Web Services 2010
I try to create a new project in Visual Studio and do this...
using Microsoft.Exchange.Webservices but Exchange is not defined.
I've tried finding it in the Add Reference... dialog with no luck...

You can find Microsoft.Exchange.Webservices.dll (Version 1.2) in the program files path.
%ProgramFiles%\Microsoft\Exchange\Web Services\1.2\

It is a NuGet package now. I had the NuGet package as a reference, but I was still getting the yellow warning symbol on the reference.
I just had to right click my project, select Manage NuGet Packages...
Then I uninstalled and reinstalled the same version. Shrug.
If you don't have the NuGet package, search for Microsoft.Exchange in the manager.