The past few days, I’ve been playing with Quartz in a .NET Core application. My goal was to create a scheduler that could trigger other services via those services having an API.
Create a .NET Core Task Scheduler with Quartz
posted on May 3, 2017 by long2know in Core, Quartz
.NET Core Angular VS2017 Templates (Part 3)
posted on April 30, 2017 by long2know in angular, Core
In Part 2 of my series on creating Angular templates for Visual Studio 2017, I made a relatively serviceable template for my latest Angular test. But, I knew it could improved.
Porting to .NET Core (Part 3)
posted on April 28, 2017 by long2know in Core
Continuing down the porting trail, there are a few more relevant things I want to share that I didn’t cover previously.
Porting to .NET Core (Part 2)
posted on April 27, 2017 by long2know in Core, Entity Framework
A while back, I started looking at ways to port EF6 code, that uses a lot of the API hooks and such, to Entity Framework Core. Over the past week, I managed to port a large scale application that was using EF6 to utilize EF Core. Here are some observations/tips in continuing with my Dotnet Core porting.
Moving from OWIN to .NET Core
posted on April 23, 2017 by long2know in ASP.NET, OWIN, Web
Since the OAuth server I’ve detailed previously is using OWIN, I’ve been looking at what it will take to move it to .NET Core. The OWIN OAuth Server provides all of the Secure Token creation. This functionality is not provided with .NET Core’s native middleware.
My first thought is to integrate with IdentityServer4 or Openiddict which provide Secure Token generation and are .NET Core compatible. After some cursory information gathering, I’m putting a few research links here for later use.
https://blogs.msdn.microsoft.com/webdev/2016/10/27/bearer-token-authentication-in-asp-net-core/
https://blogs.msdn.microsoft.com/webdev/2017/01/23/asp-net-core-authentication-with-identityserver4/
https://github.com/openiddict/openiddict-core
https://www.scottbrady91.com/Identity-Server/Getting-Started-with-IdentityServer-4
http://stackoverflow.com/questions/35304038/identityserver4-register-userservice-and-get-users-from-database-in-asp-net-core
Porting to .NET Core
posted on April 23, 2017 by long2know in Core, Entity Framework
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.
.NET Core Angular VS2017 Templates (Part 2)
posted on April 22, 2017 by long2know in angular, Core
After my last foray into finding/creating a decent Angular VS2017 template, I decided to go back to a simpler approach and update the previous template I made for Angular 2.x.
.NET Core Angular VS2017 Templates
posted on April 17, 2017 by long2know in angular, ASP.NET, Core
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.
UPDATE – Also check out my other posts on this topic:
https://blog.long2know.com/2017/04/net-core-angular-vs2017-templates-part-2/
https://blog.long2know.com/2017/04/net-core-angular-vs2017-templates-part-3/
.NET Core Strongly Typed User Configuration
posted on September 23, 2016 by long2know in ASP.NET, Core
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.
Logging with .NET Core
posted on September 22, 2016 by long2know in ASP.NET, Core
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.