Using VS2015 and asp.net 5, when I try to compile my site using an instance of System.Net.HttpClient, it tells me:
The type or namespace name 'HttpClient' could not be found (are you missing a using directive or an assembly reference?)
Hovering over the offending code, I see:
"WebApplication1.ASP.NET 5.0 - Available"
"WebApplication1.ASP.NET Core 5.0 - Not Available"
I have 2 frameworks listed in my project.json file:
"frameworks": {
"aspnet50": { },
"aspnetcore50": { }
},
I'm assuming that one of these is responsible by not having the assembly, but I don't really know how to fix it or how this works.
How can I get the site to run with HttpClient instead of throwing errors? The offending method posted below:
private async Task<string> GetStringFromUri()
{
using (var httpClient = new HttpClient())
{
result = await httpClient.GetStringAsync(
new Uri("http://baconipsum.com/api/?type=meat-and-filler"));
viewModel= result;
return viewModel;
}
}
Finally got it all worked out. @yuval set me on the right track with his answer about adding dependencies and pointing out that the class exists on github. Further searching led me to figure out that the class doesn't seem to be included in the preview release just yet, and I had to add this nuget repo to my project: https://www.myget.org/gallery/aspnetvnext
In that repo are nightly builds of the asp.net vnext nuget packages, which contained the class I want. Adding the following line to my main dependencies section and to both frameworks dependencies sections got this working for me: "Microsoft.Net.Http.Client": "1.0.0.0-rc1-10049"
"dependencies": {
[...],
"Microsoft.Net.Http.Client": "1.0.0.0-rc1-10049"
},
"frameworks": {
"aspnet50": {
"dependencies": {
"Microsoft.Net.Http.Client": "1.0.0-rc1-10049"
}
},
"aspnetcore50": {
"dependencies": {
"Microsoft.Net.Http.Client": "1.0.0-rc1-10049"
}
}
}
I've encountered the same problem today and the solution has gotten somewhat simpler in 2016.
It isn't required to add a new Nuget repository any longer.
When adding System.Net.Http
(current version 4.0.1-beta-23516), you will still get the same error if you are targeting a clr as well as a core framework version, so need to copy the dependency into the dnxcore framework dependency list, to get your code compiling.
Before:
"frameworks": {
"dnx451": {
"dependencies": {
"System.Net.Http": "4.0.1-beta-23516"
}
},
"dnxcore50": { }
}
After:
"frameworks": {
"dnx451": {
"dependencies": {
"System.Net.Http": "4.0.1-beta-23516"
}
},
"dnxcore50": {
"dependencies": {
"System.Net.Http": "4.0.1-beta-23516"
}
}
}
You need to add a new source to your nuget package manager (https://www.myget.org/F/aspnetvnext) and then add dependencies to your project.json
file. Both for dnx451
and dnxcore50
:
{
"frameworks": {
"dnx451": {
"frameworkAssemblies": {
"Microsoft.Net.Http.Client": "1.0.0-beta3-10053"
}
},
"dnxcore50": {
"frameworkAssemblies": {
"Microsoft.Net.Http.Client": "1.0.0-beta3-10053"
}
}
}
It is implemented as part of the ASP.Net xNext package, as they state on github:
Fully managed HttpMessageHandler implementation based on sockets.
This project is part of ASP.NET vNext. You can find samples, documentation and getting started instructions for ASP.NET vNext at the Home repo.
A full walkthrough can be found here
I had trouble finding in RC1 today:
For anyone who finds this question from there, HttpClient
is now in the System.Net.Http
namespace.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With