I am calling a web service from MVC controller to post data. Both stays in same solution.
My code in Web Api is:
[
HttpPost
]
public
IHttpActionResult InsertUsers([FromBody]tblUserAgentSubAgentVMWithByte tblUserAgentSubAgentVM)
{
return
Ok(
"
Success"
); }My code of controller to call web api is :
public
ViewResult Register(tblUserAgentSubAgentVM tblUserAgentSubAgentVM)
using
(
var
client =
new
HttpClient())
string
apiHost =
"
http://localhost:51522"
;
client.BaseAddress =
new
Uri(apiHost);
client.DefaultRequestHeaders.Accept.Clear();
client.DefaultRequestHeaders.Accept.Add(
new
MediaTypeWithQualityHeaderValue(
"
application/json"
));
var
json = JsonConvert.SerializeObject(tblUserAgentSubAgentVMWithByte);
var
content =
new
StringContent(json, Encoding.UTF8,
"
application/json"
);
var
result1 = client.PostAsync(
"
api/Users/InsertUsers"
, content);
}when code goes to client.PostAsync("api/Users/InsertUsers", content);, I am getting message "Id = 59, Status = WaitingForActivation, Method = "{null}", Result = "{Not yet computed}"
Why is object not being posted to API?
How can I solve the issue?
What I have tried:
Found from some article that I can not mix mix async and synchronous code like this. PostAsyn seems to be async. But I have no clue on how to not use it and call API.
Your question itself has the answer, your task has not yet been evaluated—
Result = "{Not yet computed}
. You need to give it more time, and check the result later. This time won't be known to you, since it is undefined amount of time.
That is because in the synchronous code you need to wait for the tasks
yourself
. So to say, the code becomes,
var
json = JsonConvert.SerializeObject(tblUserAgentSubAgentVMWithByte);
var
content =
new
StringContent(json, Encoding.UTF8,
"
application/json"
);
var
result1 = client.PostAsync(
"
api/Users/InsertUsers"
, content).Result;Now, the result1 will contain the result of the request. Note that this will be a blocking call, so the thread will remain blocked—in waiting state—until your request is processed, and the response is captured.
The problem is, this is not an approach that I can recommend. Although you can mix sync and async code, and it is totally valid. Think of this,
var
people = dbContext.GetPeople().Where(person =>
).ToListAsync();;
foreach
(
var
person
in
people) {
dbContext.SaveAsync();The benefit of this is, that where you know there is a delay, take the job in the background, but in the cases where a context switch is more expensive, I recommend that you stay in the same thread, do the task and generate the response.
For this sake, I recommend that you continue to use the async patterns, and write the code in async fashion.
public
async
Task<ViewResult> Register(tblUserAgentSubAgentVM tblUserAgentSubAgentVM)
using
(
var
client =
new
HttpClient())
string
apiHost =
"
http://localhost:51522"
;
client.BaseAddress =
new
Uri(apiHost);
client.DefaultRequestHeaders.Accept.Clear();
client.DefaultRequestHeaders.Accept.Add(
new
MediaTypeWithQualityHeaderValue(
"
application/json"
));
var
json = JsonConvert.SerializeObject(tblUserAgentSubAgentVMWithByte);
var
content =
new
StringContent(json, Encoding.UTF8,
"
application/json"
);
var
result1 =
await
client.PostAsync(
"
api/Users/InsertUsers"
, content);
}This way, now your runtime will automatically manage these tasks. Since you are using ASP.NET, it is way better and scalable to use async functions, than to bind the requests to threads. This is expensive. Please, do not do this.
Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad
spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or
edit the question
and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it.
Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
