Thoughts on .Net & Coding

In the Part 1 of this article you learned to implement drag-n-drop in a Blazor Server application. So far we are able to drag-n-drop files on to a drop target and list those file names in the fileBasket. However, no files are actually sent to the server. That's what we will do in this part of the article. Although our focus is going to be minimal API approach, we will explorer three variations of the process.

Uploading files from client computer to the server is a common task in web applications. You can either use jQuery Ajax or Blazor's InputFile component to accomplish that task. Files to be uploaded on the server are typically selected by the end user using file input field. However, most of the browsers also allow you to select files by dragging them from the client computer to your web application. To that end this article discusses how drag-n-drop of files can be done in Blazor Server apps. I am going to assume that you are familiar with Blazor's JavaScript interop. You may read my previous article in case you aren't familiar with Blazor's JS interop.

ASP.NET Core Blazor allows you build SPAs using C#, HTML, and CSS. Although you can develop Blazor apps without using any JavaScript, at times you might want to invoke some JavaScript code from your Blazor components. Moreover, the JavaScript code might also want to invoke some C# methods. To that end this article quickly illustrates how this can be accomplished using Blazor's JavaScript interop features.

Blazor apps consist of one or more Razor components that reside in .razor files. Usually, you place a component in a page at development time. However, at times you may want to load components on the fly based on some logic. That means you don't know the component to be loaded at the development time. That will be known only during run-time. Luckily, Blazor provides what is known as Dynamic Component that can be used to deal with such situation. In this article you will learn how Dynamic Component can be used in a Blazor Server app.

As a ASP.NET Core developer you are familiar with .NET Command Line Interface (CLI). You must have also used CLI tools such as dotnet-ef while building ASP.NET Core web apps. In addition to using built-in CLI tools you can create your own tools that can be used with .NET CLI. To this end this article introduces you to the overall tool creation and registration process.

ASP.NET Core 6 has introduced minimal APIs that provide a new way to configure application startup and routing a request to a function. In my previous article I covered the new way of configuring application startup. In this article we will see how the new routing APIs can be used to map HTTP verbs to a function.

If you are tracking the progress of ASP.NET Core 6, you are probably aware of the new features being introduced. One of the new and interesting features of ASP.NET Core 6 is the new way of configuring web application startup in just a few lines of code. Currently this new way of application startup has been introduced in empty project templates but you can easily use it in any other project template (say, ASP.NET Core MVC or Razor Pages). To that end this article shows you how standard ASP.NET Core MVC project template generated code can be modified to use the new way of application startup.

In Part 1 of this article, you learned to setup a Blazor Server app using ASP.NET Core's empty project template. Continuing further, this part teaches you to prepare a Blazor WebAssembly app using an empty project template. Since you are familiar with the basics outlined in the previous part, let's get going by creating a new empty project in Visual Studio.