What is the overhead of creating a new HttpClient per call in a WebAPI client?
What should be the HttpClient lifetime of a WebAPI client?
Is it better to have one instance of the HttpClient for multiple calls?
What should be the HttpClient lifetime of a WebAPI client?
Is it better to have one instance of the HttpClient for multiple calls?
I have a simple form with remote=true.
I have some basic code to determine errors in my MVC application. Currently in my project I have a controller called Error with action methods HTTPError404(), HTTPError500(), and General(). They all accept a string parameter error. Using or modifying the code below.
What is the best/proper way to pass the data to the Error controller for processing? I would like to have a solution as robust as possible.
In my web.config I would like to specify more than one domain for the access-control-allow-origin directive. I don’t want to use *. I’ve tried this syntax:
About 6 months ago I rolled out a site where every request needed to be over https. The only way at the time I could find to ensure that every request to a page was over https was to check it in the page load event. If the request was not over http I would response.redirect(“https://example.com“)
I have the following method to inserting data into an an access databasewhich works fine but I do get a problem if I try to insert text that contains single quotes I have learned.
All my college years I have been using public, and would like to know the difference between public, private, and protected?
I wrote REST service using ASP.NET Web API.
I’m trying to send HttpDelete request, however I get the following error:
I have created a class file in the App_Code folder in my application. I have a session variable
What is the most preferred and easiest way to do pagination in ASP.NET MVC? I.e. what is the easiest way to break up a list into several browsable pages.