Showing all posts tagged: '.NET Core'

A 5-post collection

Securing ASP.NET Core application settings using Azure Key Vault

Azure Key Vault is one of my favourite services, competing for first place with Azure Functions. And .NET Core is my favorite framework for writing applications. Imagine, then, my suprise when I found out that my favorite tools can now work together! Azure Key Vault is a cloud service for storing sensitive "secrets" and (encryption) "keys". Key Vault is simple, easy and indispensible when developing secure applications. It helps avoid the complexity of storing sensitive information in configuration files. This can be API passwords, database connections strings etc. You get the point! Previous solutions where convoluted and complex and often …[read more]


EF Core migrations with existing database schema and data

I'm currently working on an inherited .NET Core project and I'm loving the experience. I'm still using the project.json project format instead of the newer *.csproj & msbuild one. For now I'll leave it as it is but going forward I'll use the new format for subsequent ASP.NET Core projects. The project also makes use of the newest EF Core so it's all running on the edge of the .NET technology. EF Core Code First is great but the tooling is still rough around the edges. Some things are not there or some of them are not feature …[read more]


Unit testing with .NET Core

.NET Core has been in production (RTM) since June 2016, when it was officially released at the Red Had Summit by Scott Hanselman. What a glorious moment! Announcing an open source framework at a conference for Linux! Who would have thought that this would be possible 3 years ago? .NET Core may be in RTM but it's still moving at a very fast pace and there are still a lot of changes to the framework. The team announced ago .NET Standard 2.0 which comes with a few breaking changes. On top of that the tooling around .NET Core is …[read more]


Entity Framework Core 1.0 - Table Valued Functions and LINQ Composition

Entity framework Core (EFCore) has been out for a few weeks now after hitting RTM on June 27th 2016. That was also the same day that ASP.NET Core was released. EFCore has brought many changes, to say the least. It was renamed to Core instead the logical continuation from Entity Framework, because it's a total rewrite. Very similar to ASP.NET Core. The rewrite brought many benefits with speed being the biggest one. EF Core is simpler and a lot more powerful, even though it's still early days and some things are not working as expected or are missing. …[read more]


Fix OmniSharp error 'No default runtime found' in Visual Studio Code on Windows

I wanted to mess around with .NET Core on my machine and create a simple application. I'm not talking about ASP.NET Core 1.0 but .NET Core 1.0. And yes, they are different! Very different. The .NET Core applications rely on the dotnet toolchain whereas ASP.NET Core ones rely on the dnx, dnvm, dnu toolchain. Can it get any more confusing? Of course it can, just wait until you have to start targeting frameworks in your libraries. It's awesome(ly) confusing and I hope things are streamlined before we hit RTM. But until then, I want to …[read more]