The Digital Tool Factory Blog

This happens when you attempt to run and install a Visual Studio 2019 web project – after several hours of searching (and uninstalling/reinstalling things) I came across this solution from the Visual Studio Developer Community – specifically

The fix is to run the following command from an admin cmd prompt:

netsh http add iplisten ipaddress=::

and that fixed everything – note the weird syntax

My only problem with asp.net web api 2 is the inability to pass additional parameters the action, along with a base object. For example – if you want to update a contact, but keep track of where the update request came from (the location is not really part of the contact object) you cannot just add location as an additional parameter in addition to contact.

The only way of doing this is to add a parameter to the route – for example

[System.Web.Http.Route(“Ajax/v1.1/{locationArea}/SomeContactAction”)]
[OutputCache(NoStore = true, Duration = 0)]
[System.Web.Http.HttpPostAttribute]
public bool IsUniqueEmail(string locationArea,Contact contact)
{
//stuff happens
DoStuff(contact, locationArea);
return bool;
}

I recently had this problem, and after getting a new router, and a visit from Comcast, the problem turned out to be a setting, specifically the QOS Packet Scheduler. I have no idea how that setting got turned on, but turned on it was. It reduced my connection from 290 megs per second to 4.5. Quality of Service indeed. All I had to do was uncheck that box and it everything was fine again. I guess Windows 10 uses different settings for the router vs direct connection to the modem.

So, I installed a new Samsung SSD M.3 drive and found it to be much, much slower than it’s predecessor. After much sturm, drang and gnashing of teeth I stumbled across the solution. The key is in the power requirements on all things – basically just change the power profile to “Performance” in the settings and then confirm that PCI-E is set to 100%. After that it is a night and day difference.

As I’ve looked this up three times now I should put the code directly on the blog. Happily Microsoft has done a lot of the plumbing work for you.

You have a Web API controller with an action that looks like this
[System.Web.Http.Route("Ajax/v1.1/PostItemBatch")]
[OutputCache(NoStore = true, Duration = 0)]
[System.Web.Http.HttpPostAttribute]
public bool PostItemBatch(List postItems)
{
using (ApplicationDbContext db = new ApplicationDbContext())
{
foreach (PostItem postItem in postItems)
{
db.PostItems.Add(postItem);
}
db.SaveChanges();
return true;
}
}
Then you can post data to it by the following

List PostItems = new List();
for (int i = 0; i < 11; i++)
{
PostItems.Add(new PostItem(true));
}

HttpClient client = new HttpClient();
HttpResponseMessage response = client.PostAsJsonAsync("http://localhost:56168/Ajax/v1.1/PostPostItemBatch", PostItems).Result;
var test = response.IsSuccessStatusCode;

And there you go!

The root problem seems to be in the version of Newtonsoft.json – if you set it to version 11.0.1 all of the problems magically disappear