ASP.NET Core 1.0 How To Create a Self-Signed SAN Certificate - The Easy Way For a current project, I'm developing an ASP.NET Core 2.1 based multi-tenancy Web API. To test locally, I added some domains to my hosts file: 127.0.0.1 product.local 127.0.0.1 tenant-a.product.local 127.0.0.1 tenant-b.product.local In the HTTP
Node.js Node.js & ASP.NET Core 1.0: A Usage Comparison - Part 4: Cross-Origin Resource Sharing Welcome back to the fourth part of the series! Don't forget that everything explained in this post can be seen in the open-source GitHub project. The post itself contains important code pieces only. Same Origin Policy For security reasons, the browser blocks all requests from within a document or script
ASP.NET Core 1.0 Node.js & ASP.NET Core 1.0: A Usage Comparison - Part 3: Basic Routing Welcome back to the third part of the series! Don't forget that everything explained in this post can be seen in the open-source GitHub project. The post itself contains important code pieces only. In this part we take a look at basic routing capabilities. The requirements for that are pretty
Node.js Node.js & ASP.NET Core 1.0: A Usage Comparison - Part 2: Web API Server Setup Welcome back to the second part of the series! Don't forget that everything explained in this post can be seen in the open-source GitHub project. The post itself contains important code pieces only. In this part we are going to create the Web API project for both Node.js and
Node.js Node.js & ASP.NET Core 1.0: A Usage Comparison - Part 1: Intro Some days ago I was talking about Web APIs with Node.js for .NET developers at the BASTA! Conference in Darmstadt, Germany. We from Thinktecture had a blast at this great conference! My main focus in this session was giving .NET developers an overview about Node.js and how you
ASP.NET Core 1.0 Back to the roots: Creating thin Web APIs using the Core of ASP.NET Core 1.0 I'm currently fiddling about ASP.NET Core 1.0 using VS Code on my Mac. I have a simple scenario: Building a Web API which has CRUD operations for a CustomerModel. So purely HTTP things. :-) My controller looks like: using Microsoft.AspNet.Mvc; using System; using System.Collections.Generic;