Category Archives: Core

Home / ASP.NET / Core
14 Posts

I spent the better part of my development time this weekend porting various code from the .NET “full” framework to .NET Core. This included porting EntityFramework 6.1.3 code to EntityFramework Core 1.1.1. It was about as big of a pain as you would expect.

More Link

The latest tooling in Visual Studio 2017 for .NET Core is pretty good. However, it seemed like built-in templates are a bit lacking. Fortunately, the dotnet sdk, and subsequently the CLI, have libraries available for various Single Page Application framework quick starts.

More Link

Using Web.Config (or App.Config) XML files to store and retrieve settings for an application, imho, has always been a bit of a pain. Unless we write quite a bit of custom code, all we really get is a property bag of stings for our custom (user) configurations.

More Link

In most of my projects over the past two years, I’ve used Log4Net for my logging needs. Log4Net does not work, currently, with .NET Core. However, it’s pretty easy to take advantage of the new built-in logging features to wrap the Log4Net database schema using Entity Framework.

More Link

Using the .NET Core Middleware for request processing is, imho, not very well documented. There are a couple of things that are not obvious: retrieving query parameters and binding a request body to an object. To top things off, accessing the request Body has a few issues. Here’s how to deal with these scenarios.

More Link

Over the past year and a few months, we, my coworkers and I that is, have been using an Actor Model framework to implement a sort-of state-engine-based distributing computing engine. Using a generalized framework for this seemed to introduce many complexities that, in my mind, could potentially be simplified. My weekend project is centered around exploring what can be done out-of-the-box with .NET Core.

More Link

EntityFramework 7 is the defacto ORM used with .NET Core to provide cross-platform compatible data access. EF7 is missing many features that are present in EF6, though. My initial apprehension was that this would create a scenario where one could not use .NET Core if their projects relied on EF6 features. Fortunately, it’s pretty easy to get EF6 working with .NET Core. The sacrifice is a loss of cross-platform hosting ability.

More Link

In continuing to build upon my previous project to get Angular2 working with Visual Studio 2015, I’ve been playing with routing and components.

While routing and components are very different when compared to Angular v1, it’s still pretty straight forward to get a basic application up and running.

More Link

In the solution that I’m migrating to ASP.NET Core, I have a domain project that uses System.Web’s HttpContext. Since System.Web is not part of .NET Core, I had to figure out how one gets the current user’s identity within a domain class.

More Link