ASP.NET Core // Boris Wilhelms

ASP.NET Core dev-cert for Ubuntu Dec 13, 2020 - 2 min read - ASP.NET Core

While the .NET Core SDK includes an HTTPS development certificate and also has a tool to install and trust it dotnet dev-certs https --trust this unfortunately does not work on Ubuntu. The reason why it does not work on Ubuntu, or more specific on Linux in general, is that there is no standard location or api to store certificates on Linux. The paths may change from distribution to distribution. In addition application may have their own store (e.

Serverless WebApi - Host an ASP.NET Core WebApi in Azure Functions. Apr 30, 2018 - 3 min read - Azure Functions ASP.NET Core

While Azure Functions allows you to build very lightweight HTTP WebApis out of the box, the HTTP binding is very limited and sometimes we need access to the HTTP pipeline. In this post I show you how you can host a ASP.NET Core WebApi inside of a Azure Function. Prerequisites To get this working you need Azure Functions V2 Latest Azure Function Core Tools (install via npm, using npm i -g azure-functions-core-tools@core) The ASP.

Is IOptions<T> bad? Jan 24, 2018 - 6 min read - ASP.NET Core

Today I stumbled about a Tweet that suggest to not use IOptions<T> because it is a bad idea. IOption<T> is a bad idea and should not be used: https://t.co/FKlIa9iFlN — .NET Junkie (@dot_NET_Junkie) January 24, 2018 The tweet refers to a documentation page of SimpleInjector arguing why it is a bad idea to use IOptions<T>. In this post I want to investigate the arguments and describe my opinions on those.

Disable Application Insights correlation id headers on HttpClient requests in ASP.NET Core May 26, 2017 - 2 min read - Application Insights ASP.NET Core

With the upcoming version (2.1) of the Application Insights package for ASP.NET Core all requests made with HttpClient (and probably other clients) will have addition request headers, contain correlation ids. This is part of the dependency tracking feature. These headers are Request-Context, Request-Id, x-ms-request-id and x-ms-request-root-id. While this is usually not a problem, it might break functionality in some cases. For example in 2.1.0-beta2 it broke the request signature for Azure Storage requests.