How can I confirm if an async EF6 await db.SaveChangesAsync() worked as expected?
My code looks like this:
asp.net-web-api2
How I can bypass “angular-in-memory-web-api” for a specific url
I was using “angular-in-memory-web-api” to mock my REST web api, however now I am have started writing the actual web api and I want to replace the “angular-in-memory-web-api” step by step.
Why is it so hard to get route values outside controller context?
I don’t understand what’s the deal behind this, why is it so easy to get route values inside Request of controller but nearly impossible to do the same thing on HttpContext.Current.Request?
OData route exception
I am new to this so i will start with the code and after that i will explain.
The problem is this
Forcing certain code to always run on the same thread
We have an old 3rd party system (let’s call it Junksoft® 95) that we interface with via PowerShell (it exposes a COM object) and I’m in the process of wrapping it in a REST API (ASP.NET Framework 4.8 and WebAPI 2). I use the System.Management.Automation nuget package to create a PowerShell in which I instantiate Junksoft’s COM API as a dynamic object that I then use: