When I’m designing a RESTful API, I like to use the correct verbs for the correct actions, and return HTTP status codes that convey the correct message. Sure, its easy to just return a 200 OK for everything, but its a little more useful to return 204 No Content if your client shouldn’t navigate away … [Read more…]
Recently I was having an issue where a parameter being passed in to my WebAPI call was not being populated correctly. Theoretically all you need to do is add [FromBody] to the route, and it will automatically populate the object from the HTTP message’s body… but that wasn’t working for me Turns out this IS … [Read more…]
Have you ever wanted to have a web server to just return 200 OK no matter what it is fed? Basically, a web server to just say: No matter what? Recently I was working on a solution that was logging to a server that I didn’t have access to because I wasn’t inside of the … [Read more…]
I’ve found this guide on creating an Angular 4 inside of .NET core very helpful. One of the steps is to set up .NET core to serve static files: However, if you add routing to Angular 4, there’s an additional step that will allow your routes to resolve correctly in the angular application if a … [Read more…]
Newtonsoft Json.NET is a super popular (#1 most downloaded NuGet package) framework for serializing and deserializing json. In my experience, I haven’t really had to do much other than use the most basic serialization and deserialization. Sometimes, though, there is a time when the API you’re working with presents you with something goofy. In my … [Read more…]
As far as backend technologies are concerned, I really like ASP.NET and Web API. It is really easy to set up, and basically anything can talk HTTP. For front end development, I have grown to really really enjoy AngularJS. As far as an IDE is concerned, I really like Visual Studio. The problem that I’ve … [Read more…]