Coding With David

There is anew way to build web applications using C# and .Net Core, it is called Blazor.Net .   It is an experimental technology that leverages the mono run time in a browser, via web assembly, while utilizing the Razor engine from Asp.Net.     This article is not to explain the details about Blazor but to reflex on why I am excited about it and my experiences learning and using it. Here is a set of links that I have already gather to help me get started on the Blazor trail:            Blazor Documentation               Learn-Blazor            CodeDaze            Git Hub Samples            Explanation Video            BlazorFiddle.com            Video Studio          Pluralsight => Web Assembly         Pluralsight => Razor engine I have worked on the front end of web side for many years building business applications.   I would not say I know JaveScript and CSS, I can manage my way through them.   My  strength is with C#, so when I heard I can “replace

As the .Net System has grown over the last few years it can get confusing as to witch pieces are for what.   Here is a breakdown of the current frameworks available. Runtimes :     .Net Framework             ·       Around since the beginning (2002)             ·       Only runs on Windows             ·       Win Forms, WPF, ASP.Net Forms             ·       Provides a rich set of Libraries and 3 rd party components             ·       Partly open source             ·       C#, VB.Net, F#     . Net Core             ·       Fairly new (2016)             ·       Runs cross platform o    Windows o    OSX o    Linux             ·       Supports o    ASP.Net Core o    UWP             ·       Fully open source             ·       C#, VB.Net (Core 2.0)             ·       Can run truly side by side             ·       Can be self-contained (Published)     Xamarin              ·       Started as Mono              ·       Runs on o

Overview It is an open-source lightweight multi-platform ORM.  It runs on Windows, Mac OS, Linux, and UWP.  It does not contain all the features of EF6.  The goal was to learn how to use and configure EF core and if there are any advantages to using it.   I was very pleasantly surprised that is not that hard to use.  The real surprise was learning about the new features in EF core and that they were not in EF6.2.  I also learned that I could leverage some additional features from EF 6.2. New for Core Make sure you use the Microsoft NuGet package Configuration is a little more involved You must have an exe to apply for migrations Many-to-many relations are better Now support one-to-one Has a nice logging system based on Microsoft.Extension.Logger.Ilogger General logger now Filter and order are now performed on the server instead of the client Easier turning off the change tracker Easier Add and Update Migration files can be saved to source control. Like ope