Optimized ASP.NET Blazor Hosting Platform

1. Open your visual studio 2019 then click “Create a new project” option to create a new project
2. Choose “Blazor App” then click Next
3. Configure your project name and location, then create it.
4. Choose the .net core version and choose the Blazor App type, then click “Create” button to create your Blazor App.
5. If you want to publish this project to our server, please right-click the project name and click publish option to publish your project. On the Publish page please choose the “Import Profile” option and click “Next”.
6. You can get our server publish setting info from your Plesk Control Panel.
7. Then click “Browse…” button to import our configuration file
8.  Then enter the web deploy publish password (same as your Control Panel password by default) to publish your project.
9. When your project publishes to our server you can use the browser to test it.

ASP.NET Core 5.x, .NET Core 3.x, and .NET Core 2.x are all supported, in both framework-dependent deployment (FDD) and self-contained deployment (SCD) modes. Core versions not listed can be deployed self-contained until the framework is installed.

Most versions of Visual Studio and Visual Web Developer are supported. You may run in to issues with some older versions. .NET Core 6.0 requires Visual Studio 2022.

. NET 6 is the fastest full stack web framework, which lowers compute costs if you’re running in the cloud. Ultimate productivity: . NET 6 and Visual Studio 2022 provide hot reload, new git tooling, intelligent code editing, robust diagnostics and testing tools, and better team collaboration.

Previousely, .NET Core 5.0 Brought You:

• MVC model binding improvements, including support for C# 9 record types
• OpenAPI Specification on by default
• Authorization while using endpoint routing
• JSON extension methods for HttpRequest and HttpResponse

When the Blazor WebAssembly app is created for deployment without a backend ASP.NET Core app to serve its files, the app is called a standalone Blazor WebAssembly app. When the app is created for deployment with a backend app to serve its files, the app is called a hosted Blazor WebAssembly app.

The Blazor WebAssembly (WASM) hosting model offers several benefits:

• There’s no .NET server-side dependency after the app is downloaded from the server, so the app remains functional if the server goes offline.
• Client resources and capabilities are fully leveraged.
• Work is offloaded from the server to the client.
• An ASP.NET Core web server isn’t required to host the app. > – Serverless deployment scenarios are possible, such as serving the app from a Content Delivery Network (CDN).
  
  

The Blazor WebAssembly hosting model has the following limitations:

• The app is restricted to the capabilities of the browser.
• Capable client hardware and software (for example, WebAssembly support) is required.
• Download size is larger, and apps take longer to load.

Versus Blazor Server:

The Blazor Server hosting model offers several benefits:

• Download size is significantly smaller than a Blazor WebAssembly app, and the app loads much faster. -The app takes full advantage of server capabilities, including the use of .NET Core APIs.
• .NET Core on the server is used to run the app, so existing .NET tooling, such as debugging, works as expected.
• Thin clients are supported. For example, Blazor Server apps work with browsers that don’t support WebAssembly and on resource-constrained devices.
• The app’s .NET/C# code base, including the app’s component code, isn’t served to clients.
  
  

The Blazor Server hosting model has the following limitations:

• Higher latency usually exists. Every user interaction involves a network hop.
• There’s no offline support. If the client connection fails, the app stops working.
• Scaling apps with many users requires server resources to handle multiple client connections and client state.
• An ASP.NET Core server is required to serve the app. Serverless deployment scenarios aren’t possible, such as serving the app from a Content Delivery Network (CDN).