This is my personal opinion and I have a good reason to recommend developers to move to .NET Core instead of .NET Framework. Some might disagree with my opinion, but hey, it’s good to share thoughts and to discuss it. I’m not going to tell what is .NET Framework as you can just Google it, but I can assure you that .NET Framework can only be run on a Windows Operating System machine.

Drawing The Line

There will always be a reason for developers or their team lead to saying that their system is still using old system which is obviously happen to enterprise developers. So, I will draw some lines on who should move to using .NET Core instead of .NET Framework. Here is what is in my mind:

If you are a maintainer of a legacy Windows services backend, web apps or web services, than you need to keep using .NET Framework for now.

If your apps will be deployed on an old Windows Server machines, than you might want to stick with .NET Framework for now.

If you are a VB developers which only relied on VB.NET language, than you have to use .NET Framework.

If you are sure that your system won’t be deployed to a cloud very soon, than you can stick with .NET Framework for now.

If you are stuck without any option whatsoever to use .NET Framework, than you need to continue using .NET Framework.

Beginners, just learn .NET Core instead!

Bot Application with BotBuilder SDK

To create a chat bot application using .NET Framework, you might already know this type of Bot Application template when launching new project in Visual Studio 2017.

The problem is, the NuGet packages and the template project which is from the BotBuilder SDK currently only support .NET Framework 4.6 and above as stated on the page and not yet supporting .NET Core related. Here is the message from the docs page:

Last year I tried and make an article on Windows 10 UWP app for Desktop and Windows Mobile (a.k.a. Windows Phone) to work with ASP.NET Core SignalR (the early version). As currently the ASP.NET Core team released the SignalR Core 1.0.0-alpha1-final and the .NET team has released the remarkable and awesome .NET Core 2.0, .NET Standard 2.0 and the latest Xamarin 2.4.0 that is compatible with .NET Standard 2.0, I would like to try this in Xamarin mobile apps that is for Android and iOS.

It turn out awesome and I love it. The demo that I created is a very simple UI (User Interface) of Label and Slider controls. Project on the solution:

It has been quite sometimes I have not use ASP.NET SignalR. As you may know that currently we can use ASP.NET Core for creating WebAPI, it come to my mind to try SignalR service using ASP.NET Core and with Windows 10 UWP as the client for consuming the SignalR service. This blog is about just that, I divide the project into two, that is the SignalR service server and SignalR client which is inside Windows 10 UWP app. So let’s start.

Using the asp-fragment for Named Anchor

Recently I’m playing around with the ASP.NET Core MVC tag helpers. I’m very impressed with tag helper to resolve anchor link which are more readable and clean compare to the previous ASP.NET Framework MVC that mixes with C#. However, I got some situation which needs to be resolve using the anchor tag helper, that is using the Named Anchor.

Microsoft Edge is definitely a Modern Browser which renders HTML5 Web Standards, technically similar to IE11, Chrome, Firefox, Opera and Safari browsers. However, Microsoft Edge is very different with other browsers since there is no such as BHO (Browser Helper Object) or can run ActiveX components and Plugins. It may have extensions soon but that is not what I’m going to share on this article.Read More