If you have ever tried to implement a similar self-contained UI in one of your projects you may have found it quite difficult to set up. The development workflow can also be a bit of a pain. You may have had to make trade-offs on development features like editing your HTML and seeing it refresh without having to recompile the app.
In the comments of my last post, I got asked to write about how to create an email form using ASP.NET Core Razor Pages. The reader also asked about a tutorial about authentication and authorization. I’ll write about this in one of the next posts. This post is just about creating a form and sending an email with the form values.
Creating a New Project
To try this out, you need to have the latest Preview of Visual Studio 2017 installed (I use 15.3.0 Preview 3) and you need .NET Core 2.0 Preview installed (2.0.0-preview2-006497 in my case).
In this article, we will learn ASP.NET Core using Angular 2 in Visual Studio 2017.
Why should we use Angular 2?
Why should we use ASP.NET Core?
What should we know about?
How do we use Angular 2 in ASP.NET Core?
Why Should We Use Angular 2?
Angular 2 is a great framework to use for getting the most out of the latest browsers and thus for creating better applications. Angular 2 can build applications that live on:
With ASP.NET Core 2.0 Preview 2, there are new web application templates available for Single Page Applications (SPA). Currently Angular, React.js and React.js + Redux are supported. This blog post gives a short overview of new templates and related sample applications.
New SPA Templates
When creating a new ASP.NET Core application using Visual Studio 2017 Preview 3, there are now three new templates available for SPAs as shown in the screenshot below.
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.