WebInspect is an example of a test harness.

A test harness tests a thing in an automated fashion, cooking up its own set of tests, in many ways from many angles and not just in a handful of happy pass scenarios.

Angular 7 is here as of this week (yesterday).

It looks like there will be drag-and-drop functionality for the CDK! Another CDK thing of 7 is virtual scrolling in which parts of the DOM are unloaded or loaded (based upon what is visible in a scrollable list) creating a performance gain.

Universal Date and Time Format

Per the World Wide Web Consortium it is:

YYYY-MM-DDThh:mm:ss.sTZD

 
 

...and their example here is:

1997-07-16T19:20:30.45+01:00

 
 

That is not the same as this format which will play nicely with both T-SQL and PL/SQL and that's kinda frustrating.

Edit Bindings...

If you right-click on a web site under Sites in IIS at Windows Server 2012 R2 you will see an option for either "Edit Bindings..." or "Bindings..." depending upon where you click and this will give you a list of host headers for that web site to add to or edit.

Refresh

In Windows Server 2012 R2 if you right-click on the Windows symbol start bar thing at the lower left corner and you pick "Programs and Features" the Programs and Features list may be refreshed by clicking the circular arrow at the right end of what kinda looks like a URL bar in a browser. In the Services pane, instead and in contrast, go to: Action > Refresh

Press Ctrl+Alt+a in SQL Server 2016 Management Studio to open the Activity Monitor.

There is also an icon for it in the Standard toolbar that kinda looks like a graph with some thing sitting at its lower right corner. View > Toolbars > Standard ...should unlock this menu/toolbar if you do not see it. There is an "accordion" for Processes inside, and here you may right-click on Processes to kill them. You may kick other users out of the database in advance of making sweeping changes in this manner.

other things you may return for an IActionResult in .NET Core's MVC

Beyond returning a JsonResult when things go right, you may return stuff like this when things go South:

• return NotFound(new { Error = ourSpecificError });
• return new StatusCodeResult(500);
• return new OkResult();

 
 

These are revealed on pages 202 to 205 of "ASP.NET Core 2 and Angular 5" by Valerio De Sanctis. I don't yet know how you ideally consume the errors with Angular 5. I guess I will find that out as I keep reading.