Skip to content

Commit a6744f4

Browse files
Merge pull request #7046 from syncfusion-content/985195-Merge
Cleared the conflicts in move the changes from hotfix to development
2 parents 27f884d + 07b8f78 commit a6744f4

32 files changed

+381
-212
lines changed

blazor-toc.html

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -364,8 +364,18 @@
364364
<li>
365365
<a href="/blazor/common/html-attributes">HTML Attributes</a>
366366
</li>
367-
<li>
368-
<a href="/blazor/common/deployment">Deployment</a>
367+
<li>Deployment
368+
<ul>
369+
<li>
370+
<a href="/blazor/common/deployment/publish">Publish Blazor Application</a>
371+
</li>
372+
<li>
373+
<a href="/blazor/common/deployment/deployment-iis">Deploy a Blazor Web App to IIS</a>
374+
</li>
375+
<li>
376+
<a href="/blazor/common/deployment/deployment-azure">Deploy a Blazor Web App to Azure App Service</a>
377+
</li>
378+
</ul>
369379
</li>
370380
<li>
371381
<a href="/blazor/common/cdn-fallback">CDN Fallback</a>
Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
---
2+
layout: post
3+
title: Deploy a Blazor Web App to Azure App Service | Syncfusion
4+
description: Learn here all about deploying the Blazor application with Syncfusion Blazor Components to Azure App Service.
5+
platform: Blazor
6+
component: Common
7+
documentation: ug
8+
---
9+
10+
# Deploy Blazor Web App to Azure App Service
11+
12+
This section provides information about deploying a Blazor Web applications with the Syncfusion Blazor components to Azure App Service.
13+
14+
Refer to [Host and deploy ASP.NET Core Blazor](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-7.0&tabs=visual-studio) topic for more information.
15+
16+
## Deployment procedure
17+
18+
If you don’t have a login for Azure, [sign up](https://azure.microsoft.com/en-in/free/) to access the Azure Portal.
19+
20+
### Create a resource in Azure
21+
22+
* Click **Create a resource** in Azure Portal to create a resource group.
23+
24+
![Create new resource](../images/create-new-resource.png)
25+
26+
* Select **Web App** Azure application service.
27+
28+
![Select web app](../images/web-app.png)
29+
30+
* After selecting Web App option, choose an appropriate resource group name and instance details.
31+
32+
* Once this is done, click **Review + create**.
33+
34+
![Create resource](../images/create-resource.png)
35+
36+
* After configuring the Web App service. Select the created web app service (blazor-web-publish).
37+
38+
![Created resource](../images/created-resource.png)
39+
40+
* Now, select the **overview** section, click on **Download publish profile**, and save the profile locally.
41+
42+
![Download publish profile](../images/download-publish-profile.png)
43+
44+
### Publish the Application in Azure
45+
46+
#### Using Azure account login
47+
48+
* To publish the project, right-click on it and choose **Publish** from the context menu.
49+
50+
![Publish menu](../images/publish-menu.png)
51+
52+
* Select **Azure** as the target and **Azure App Service (Windows)** as the specific target.
53+
54+
![Publish target](../images/publish-target.png)
55+
56+
![Publish specific target](../images/publish-specific-target.png)
57+
58+
* You need to log into your Azure account and choose the web app service (blazor-web-publish) that you have created. Then, click **Publish**.
59+
60+
![Created azure app service](../images/created-azure-resource.png)
61+
62+
![Publish App](../images/publish-azure.png)
63+
64+
#### Using Import Profile option
65+
66+
* To publish the project, right-click on it and choose **Publish** from the context menu.
67+
68+
![Publish menu](../images/publish-menu.png)
69+
70+
* Select **Import Profile** as the target and browse the downloaded publish folder. Then, click **Publish**
71+
72+
![Publish target](../images/target-import-profile.png)
73+
74+
![Publish App](../images/publish-azure.png)
75+
76+
* Now, the application will be deployed and will be available in the specified URL: https://blazor-web-publish.azurewebsites.net/.
77+
78+
![Output-Azure](../images/output-azure.png)
79+
80+
## See also
81+
82+
Refer [here](https://learn.microsoft.com/en-us/azure/app-service/quickstart-dotnetcore?tabs=net70&pivots=development-environment-vs#publish-your-web-app) for publishing the application to Azure App Service using Visual Studio.
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
layout: post
3+
title: Deploy a Blazor Web App to IIS | Syncfusion
4+
description: Learn here all about deploying the Blazor application with Syncfusion Blazor Components to IIS server.
5+
platform: Blazor
6+
component: Common
7+
documentation: ug
8+
---
9+
10+
# Deploy Blazor Web App to IIS server
11+
12+
This section provides information about deploying a Blazor Web applications with the Syncfusion Blazor components to IIS server.
13+
14+
Refer to [Host and deploy ASP.NET Core Blazor](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-7.0&tabs=visual-studio) topic for more information.
15+
16+
## Create an IIS Site
17+
18+
* [Enable IIS](https://learn.microsoft.com/en-us/previous-versions/dynamicsnav-2018-developer/How-to--Install-and-Configure-Internet-Information-Services-for-Microsoft-Dynamics-NAV-Web-Client)in Windows Features.
19+
20+
* [Enable WebSockets](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/websockets?view=aspnetcore-7.0#enabling-websockets-on-iis) in IIS.
21+
22+
* Now, publish the application for deployment in Release configuration by referring to [this](https://blazor.syncfusion.com/documentation/common/deployment).
23+
24+
* Open Internet Information Services (IIS) Manager and then right-click on "Sites," followed by selecting "Add Website."
25+
26+
![Add site in IIS](../images/add-site.png)
27+
28+
* In the Add Website dialog, fill in the required field values such as site name, physical path and customized port value and then click OK.
29+
30+
Set the physical path to the location where your sample application is developed.
31+
32+
![Add Website in IIS](../images/add-website.png)
33+
34+
## Run the Published Application
35+
36+
* Open Internet Information Services (IIS) Manager. Expand the `Sites` node to verify that the published application is running. Click `Browse` to open the application in your browser.
37+
38+
![Browse application](../images/browser-website.png)
39+
40+
* Now, application runs in the specified browser port(8080).
41+
42+
![Output-IIS](../images/iis-output.png)
43+
44+
## See also
45+
46+
Refer [here](https://learn.microsoft.com/en-us/aspnet/core/tutorials/publish-to-iis?view=aspnetcore-7.0&tabs=visual-studio) for publishing the application to IIS Service using Visual Studio.

blazor/common/deployment.md renamed to blazor/common/deployment/publish.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,25 +11,25 @@ documentation: ug
1111

1212
This section provides information about publishing and deploying Blazor applications with the Syncfusion Blazor components.
1313

14-
For more information, see [Host and deploy ASP.NET Core Blazor](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy).
14+
Refer to [Host and deploy ASP.NET Core Blazor](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-7.0&tabs=visual-studio) topic for more information.
1515

1616
## Publish Blazor Application with Visual Studio
1717

1818
* Right-click on the project in the `Solution Explorer` and select `Publish`.
1919

20-
![Solution Explorer in Blazor](./images/publish.png)
20+
![Solution Explorer in Blazor](../images/publish.png)
2121

2222
* Then, select the `Folder` option and select the publishing target location.
2323

24-
![Publish Location in Blazor](./images/folder.png)
24+
![Publish Location in Blazor](../images/folder.png)
2525

2626
* Check the configuration as Release by clicking the `Advanced...` option below the target location.
2727

28-
![Release Configuration in Blazor](./images/config.png)
28+
![Release Configuration in Blazor](../images/config.png)
2929

3030
* For `Blazor Server side application`, set Deployment Mode as `Self-Contained`. Because some dependencies are not loaded properly when the published folder is hosted.
3131

32-
![Deploy Mode in Blazor](./images/deploy.png)
32+
![Deploy Mode in Blazor](../images/deploy.png)
3333

3434
* Then, click `Save` and `Publish`.
3535

@@ -59,7 +59,7 @@ dotnet publish -c Release --self-contained true -r win-x86
5959
{% endhighlight %}
6060
{% endtabs %}
6161

62-
Refer to [dotnet publish arguments](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish#arguments) to learn about optional arguments. Use the following command to specify the output directory path.
62+
Refer to the [dotnet publish - arguments](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish?tabs=netcore21#arguments) to learn about various optional arguments. Use the following command to specify the path for the output directory.
6363

6464
{% tabs %}
6565
{% highlight c# tabtitle=".NET CLI" %}
@@ -75,7 +75,7 @@ If the path is relative, the output directory generated is relative to the proje
7575

7676
## Ahead-of-time (AOT) compilation in Blazor WebAssembly
7777

78-
Blazor WebAssembly supports ahead-of-time (AOT) compilation, which improves runtime performance at the expense of a larger app size. For details and enable steps, see [Ahead-of-time (AOT) compilation](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly#ahead-of-time-aot-compilation).
78+
Blazor WebAssembly supports ahead-of-time (AOT) compilation which provides improved runtime performance at the expense of a larger app size. Refer to [Ahead-of-time (AOT) compilation](https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-6.0#ahead-of-time-aot-compilation) topic to learn more about how it works and how to enable.
7979

8080
### Enable AOT in the application
8181

blazor/common/images/add-site.png

71.1 KB
Loading
99.7 KB
Loading
88.9 KB
Loading
41.9 KB
Loading
95.7 KB
Loading
29.4 KB
Loading

0 commit comments

Comments
 (0)