Deploying a Blazor Application on IIS
Deploying a Blazor Application on IIS
Learn how to deploy an ASP.NET Core hosted Blazor application in this tutorial, using IIS 10 on a Windows 10 machine.
Join the DZone community and get the full member experience.Join For Free
In this article, we will understand how to deploy an ASP.NET Core hosted Blazor application with the help of IIS 10 on a Windows 10 machine. We will be using Visual Studio 2017 to publish the app and SQL Server 204 to handle DB operations. We will also troubleshoot some of the common hosting issues for a Blazor application.
Please refer to my previous article Cascading DropDownList in Blazor Using EF Core to create the application that we will be deploying in this tutorial.
Installing .NET Core Hosting Bundle
Since we are going to deploy an ASP.NET Core hosted Blazor application, the first step is to install .NET Core hosting bundle on our machine.
Follow the below steps to download .NET Core hosting bundle:
Select the latest non-preview .NET Core runtime from the list. For this tutorial, we will select .NET Core Runtime 2.0.7. Refer to the image below:
On the .NET Core runtime download page, scroll down to Windows section, select the “Hosting Bundle Installer” link to download the .NET Core Hosting Bundle.
Once the download is finished, double-click to start installing it. You can see a window similar to the one shown below:
- .NET Core hosting bundle should be installed after installing IIS only. If you install.NET Core hosting bundle before installing IIS then you need to repair it after installing IIS so that it will update its dependencies for IIS.
- Restart the machine after installing .NET Core hosting bundle.
Publishing the Blazor Application
Once .NET Core hosting bundle installation is successful and you have restarted your machine, open the Blazor application solution using VS 2017.
Right-click on Server project of your solution and click publish. In this case, it will be BlazorDDL.Server >> Publish
You will see a screen similar to below. Select Folder from the left menu and provide a folder path. You can provide any folder path where you want to publish your app.
Click on publish. Visual Studio will start publishing your application. If there are no build errors then your application will be published successfully to the folder you have chosen.
After the publishing is successful, we will move on to configure IIS.
Open IIS and right click on Sites >> Add Web Site.
An "Add Website" pop up box will open. Here we need to furnish details in three fields
- Site name: Put any name of your choice. Here I put "ankitsite."
- Physical Path: The path to the folder where you have published your application.
- Hostname: This is the name we put in the browser to access our application. We will put ankitsite.com for this demo.
Refer to the image below:
Next step is to configure the "Application Pool" for our site. The application pool name will be same as the "Site name" we provided in the last step. Therefore, in this case, the application pool name will be "ankitsite." Click to "Application Pools" from the left panel and double click on the pool "ankitsite." It will open an "edit application pool" window. Select "No Managed Code" from the .NET CLR version drop-down. Refer to the image below:
Here is the whole process of configuring IIS explained in a gif image.
Configuring the DNS Host
The last step is to configure our DNS host file.
Navigate to C:\Windows\System32\drivers\etc path in your machine and open the "hosts" file using any text editor.
We need to add the hostname that we provided in IIS against localhost IP address. Refer to the image below:
This shows we have successfully hosted a Blazor application on IIS.
Open any browser on your machine and enter the hostname you have configured. You can see that the application will open in the browser window.
Troubleshooting Common Hosting Issues
In this section, we will look into some of the common problems that you can face while hosting a Blazor application.
1. If You Are Unable to Open the Website and Get a DNS Not Found Error
Check if the hostname is configured correctly in the host file. Make sure that your machine is not connected to any VPN server. Also, if you are using any Web proxy then disable it.
2. HTTP Error 500.19 – Internal Server Error – "The requested page cannot be accessed because the related configuration data for the page is invalid."
This error is clear. The publish folder is inaccessible because of insufficient permissions. Add the current windows user to the list of users with permissions over that folder.
3. If the Website Is Loading but Data Is Not Getting Populated and You Get a 500 Internal Server Error
Make sure that your connection string is in the correct format. The user id that you have specified in your connection string should have db_datareader and db_datawriter permissions. If the issue persists then provide the user with db_owner permission.
4. If the Data Is Not Getting Populated and You Get an “Operation Not Allowed” Exception
This issue generally appears when you try to do a PUT, POST or DELETE operation in your web API. To mitigate this issue we need to alter the configuration of IIS.
Navigate to Control Panel >> Turn Windows feature on or off. Then navigate to Internet Information Services >> World Wide Web Services >> Common HTTP Features and uncheck the "WebDAV Publishing" option and click ok. Refer to the image below:
The cause of this error is that the client and the server of the application are not on the same port. The browser will restrict the application to make web API calls due to same-origin policy.
To resolve this issue you need to enable Cross-Origin Requests (CORS) in your application. Please refer to Microsoft documents on Enable Cross-Origin Requests (CORS) in ASP.NET Core.
In this article, we learned how to deploy a Blazor application on IIS in windows machine. We also learned how to resolve some of the common hosting issues while deploying a Blazor application.
You can check out my other articles about Blazor here.
Published at DZone with permission of Ankit Sharma , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.