Service Fabric projects have evolved at what feels like a break-neck pace, along with the .NET Core platform and tooling, and with the recent release of Visual Studio 2017, no doubt you are considering the productivity merits of upgrading (container support). For Service Fabric projects designed in Visual Studio 2015 and using the .Net Core .xproj/project.json structures now deprecated in Visual Studio 2017, the automatic upgrade process may result in only partial conversion success.
In this article, we’ll take a look at the issues encountered while upgrading a .NET Core Service Fabric solution containing 77 .xproj/project.json projects to Visual Studio 2017.
There is a number of Web APIs which allow you to measure the performance of web applications:
User Timing API (access to high precision timestamps).
Resource Timing API (timing information related to resources on a document).
Navigation Timing API (timing information related to navigation and elements).
The youngest member of the family is Server Timing API which allows for communicating the server performance metrics to the client. The API is not widely supported yet, but Chrome Devtools is able to interpret the information sent from the server and expose it as part of the request timing information. Let’s see how this feature can be utilized from ASP.NET Core.
What Is the ASP.NET Web API?
ASP.NET Web API is a framework to build web APIs on top of the .NET framework, which makes it easy to build HTTP services that comprise of a range of clients, including mobile devices, web browsers, and desktop applications.
Web API is similar to ASP.NET MVC, so it contains all of MVC’s features.
When you want to run a .NET Core process as a daemon on Red Hat Enterprise Linux, you can create a custom systemd unit. Today, I’ll write about two examples of custom systemd units for .NET Core. One is a oneshot type for running a .NET Core console application and the other is a simple type for running an ASP.NET Core Web application.
Oneshot Type With a Console Application
Building an App
You can use dotnet run in systemd with the specifying project directory as a working directory. However, let’s build a binary file and use it for systemd. Create your project with dotnet new and edit Program.cs as follows:
Hangfire is one of the easiest ways to perform background processing in .NET and .NET Core Applications. In this application we are going to learn how we are can integrate Hangfire with ASP.NET Core applications.
Hangfire allows you to create background tasks in .NET applications. It’s extremely easy to integrate. It allows you to kick off method calls outside of the request processing pipeline in very easy but reliable ways. You can store those jobs in on-premise SQL Servers, SQL Azure, Redis, or MSMQ.
This blog post shows you how to log messages to a Syslog server from ASP.NET Core applications.
The Syslog server is a popular logs server from the Linux world. It is usually a separate box or virtual machine that accepts log messages but it is not accessible by external users. It can be especially useful for web applications, as hackers can’t open a way to your internal network, and thus logs remain safe, as malicious users cannot access them.
In this article, we will explain how to create a QR Code Generator in ASP.NET Core 1.0, using Zxing.Net.
I tried to create a QR Code Generator in ASP.NET Core, using third party libraries. But in most cases, barcodes are not fully supported in ASP.NET Core because of some version issues, etc. I searched a lot in Google but finally, I found “Zxing.Net” – a library which supports the decoding and generating of barcodes. I had a discussion with MicJahn and came up with a great solution.
I have a couple of small open-source projects out there. For me, the hardest part of getting such projects into a state which allows others to use them effectively is creating documentation – I only have enough discipline to put triple-slash-comments on the public API. In the past, I’ve been using Sandcastle Help File Builder to create help files based on that, but it slowly starts to feel heavy and outdated. So when Microsoft announced the move of .NET Framework docs to docs.microsoft.com with information that it is being powered by DocFX, I decided this is what I would try the next time I had to set up documentation for a project. Also, based on my previous experience, I’ve set some requirements:
The documentation needs to be part of the Visual Studio solution.
The documentation should be generated on the build.
The documentation should be previewable from Visual Studio.
When Lib.AspNetCore.Mvc.JqGrid reached the v1.0.0 I had the opportunity to try to do this.
ASP.NET Core 2 comes with Razor Pages that allow developers to build simple web applications with less overhead compared to MVC. The emphasis is on the word “simple” as Razor Pages doesn’t come with patterns suitable for bigger and more complex applications. For this, we have MVC that is flexible enough to build applications that will grow over years. This blog post uses a simple shoutbox application to illustrate how to build applications using Razor Pages.
This post introduces how to build a simple and primitive shoutbox application using ASP.NET Core and Razor Pages. We will also use SQL Server LocalDb and Entity Framework Core code-first to make things more interesting. The goal of this post is to demonstrate how to use Razor Pages pages with and with-out a backing model.
Unfortunately, a newly started ASP.NET Core Application doesn’t include a complete configuration as a sample. This makes the jump-start a little difficult. The new Configuration is quite better than the old one and it would make sense to add some settings by default. Anyway, let’s start by creating a new Project.
Open the Startup.cs and take a look at the controller. There’s already something like a configuration setup. This is exactly what the newly created application needs to run.