In previous post, I showed you how to implement a custom migration without using Entity Framework for Sqlite database in .Net core. In this post, I’ll use Entity Framework Migration to manage (upgrade / downgrade) our database structure. Both of approaches will work, you can choose one of 2 solutions as you prefer.
With the growth of many cheap Linux VPS providers and the new releas of .NET core, we have a possibility to host our applications with a low cost. In this post, I would like to write down the steps how I published a ASP.NET core application to a Linux VPS. The application is just a simple “Hello World!” ASP.NET core. The code will be compiled and deployed manually on the Linux VPS. In praxis, you can automatically deploy your app over FTP or use Git to check out the release branch, build and deploy.
In last months there were 2 big frameworks for software development published: DotNetCore and Angular 2. They’re new and powerful. I’ve spent most of my free time to learn both of them. The combination of DotNetCore Web Api and Angular 2 give me a powerful development enviroment for building website or building web-view app (based on Apache Cordova). I’ve started to build some web apps with Angular 2 (for example YouTubeApp or my private dictionary EnDeVi). They are all my pet projects but it’s a good start for learning new stuffs. In this blog, I would like to write about DotNetCore and Sqlite like the previous post Sqlite with Entity Framework Code First and Migration. Basically there’s nothing new with this post, I just want to test how I can write a simple .NET core console connecting to Sqlite database.