.NET Framework and .NET Core are two different platforms implementing the .NET standard. Here are some key differences between them:

1. **Cross-Platform Support**:
.NET Framework is only available for the Windows operating system, while .NET Core is cross-platform and works on various operating systems, such as Windows, Linux, and MacOS.

2. **Application Models**:
.NET Framework supports various application models, including Windows Forms, WPF, and ASP.NET. .NET Core, on the other hand, initially had limited application models, mainly console and ASP.NET Core. Starting from version 3.0, .NET Core also began to support WPF and Windows Forms, but only on Windows.

3. **Microservices Support**:
.NET Core is a better choice for microservices due to its modular and lightweight nature. It allows creating small, independent services that can be developed and scaled independently. .NET Framework, on the other hand, is not recommended for microservice architecture.

4. **Performance**:
.NET Core is more efficient and faster compared to .NET Framework thanks to various improvements and optimizations.

5. **Version Support**:
.NET Core offers better support for different versions. In .NET Core, you have better control over the version of the runtime environment being used. In .NET Framework, updates usually affect the entire system and can cause compatibility issues.

**Kestrel** is a web server that is used by default in ASP.NET Core when creating web applications. It is a cross-platform server, meaning it operates on various operating systems such as Windows, Linux, and macOS.

**Kestrel** can handle both small and large projects, making it a versatile choice for developers. The most important feature of this server is its very good performance, especially when compared to previous servers used in ASP.NET.

However, it is one of many servers that can be used in ASP.NET Core. It can be replaced with another, such as IIS or HTTP.sys, if needed. Kestrel is the default choice when creating new applications in ASP.NET Core due to its performance and versatility. Additionally, it is fully configurable, giving developers full control over how the server operates.

**Hot Reload** is a feature in .NET that allows developers to modify the source code of an application while it is running, without needing to stop and restart the application. The modified code is immediately compiled and injected into the running application.

This means that if you make changes to the view or business logic, you don't need to stop and restart your application to see these changes live. This improves development efficiency, saving time and eliminating (or at least reducing) interruptions caused by restarting.

Hot Reload is currently available for console applications, WPF applications (.NET Core 3.1 and later), Windows Forms applications (.NET 6.0 and later), and ASP.NET Core applications (excluding Blazor applications).

A distinguishing feature of this functionality is that it can be used without the need to attach a debugger, making its use even more efficient in everyday application development. Hot Reload works in both Debug and Release modes.

Global Tool is a special type of NuGet package that contains a console application. This tool is installed globally on the computer and can be used from anywhere in the system.

This can be useful in many situations, for example, when you want access to a specific .NET Tool function without adding it as a dependency to every project. An example of a Global Tool is .NET Watcher, which automatically builds and runs the application when it detects changes in the source code.

To install Global Tools, the command `dotnet tool install -g` is used, where the `-g` option indicates installing the tool globally. To uninstall, `dotnet tool uninstall -g` is used.


There is also the option to install the tool locally for a specific project using the `--tool-path` option. This can be useful if you want to use different versions of tools for different projects.